From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: David Miller <davem@davemloft•net>,
Networking <netdev@vger•kernel.org>,
Cai Huoqing <caihuoqing@baidu•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the staging tree
Date: Mon, 16 Aug 2021 07:24:33 +0200 [thread overview]
Message-ID: <YRn2kUHl2hVFPggS@kroah.com> (raw)
In-Reply-To: <20210816135216.46e50364@canb.auug.org.au>
On Mon, Aug 16, 2021 at 01:52:16PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/staging/r8188eu/core/rtw_br_ext.c:8:10: fatal error: ../include/net/ipx.h: No such file or directory
> 8 | #include "../include/net/ipx.h"
> | ^~~~~~~~~~~~~~~~~~~~~~
>
> Caused by commit
>
> 6c9b40844751 ("net: Remove net/ipx.h and uapi/linux/ipx.h header files")
>
> from the net-next tree.
>
> I have reverted that commit for today.
>
That's not fair to the networking developers, I'll work on a patch for
this driver to remove that later today...
thanks,
greg k-h
next prev parent reply other threads:[~2021-08-16 5:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 3:52 linux-next: build failure after merge of the staging tree Stephen Rothwell
2021-08-16 5:24 ` Greg KH [this message]
2021-08-16 15:10 ` Greg KH
2021-08-16 21:46 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2015-06-03 7:16 Stephen Rothwell
2015-06-03 7:23 ` Johannes Berg
2011-08-25 5:02 Stephen Rothwell
2011-08-25 5:15 ` Larry Finger
2011-08-25 15:39 ` Greg KH
2011-07-06 5:02 Stephen Rothwell
2011-07-06 15:12 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YRn2kUHl2hVFPggS@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=caihuoqing@baidu$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox