From: Greg KH <greg@kroah.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Phillip Potter <phil@philpotter.co.uk>
Subject: Re: build failure after merge of the staging tree
Date: Fri, 30 Jul 2021 16:02:41 +0200 [thread overview]
Message-ID: <YQQGgReGba/Ld40y@kroah.com> (raw)
In-Reply-To: <20210730135340.17863-1-broonie@kernel.org>
On Fri, Jul 30, 2021 at 02:53:40PM +0100, Mark Brown wrote:
> Hi all,
>
> After merging the staging tree, today's linux-next build (x86
> allmodconfig) failed like this:
>
> /tmp/next/build/drivers/staging/r8188eu/core/rtw_ap.c:22:10: fatal error: osdep_service.h: No such file or directory
> #include <osdep_service.h>
> ^~~~~~~~~~~~~~~~~
> compilation terminated.
> make[4]: *** [/tmp/next/build/scripts/Makefile.build:271: drivers/staging/r8188eu/core/rtw_ap.o] Error 1
> make[4]: *** Waiting for unfinished jobs....
> /tmp/next/build/drivers/staging/r8188eu/core/rtw_br_ext.c:29:10: fatal error: drv_types.h: No such file or directory
> #include <drv_types.h>
> ^~~~~~~~~~~~~
> compilation terminated.
>
> Caused by commit
>
> 15865124feed880978b7 ("staging: r8188eu: introduce new core dir for RTL8188eu driver")
>
> I've used the staging tree from yesterday instead.
Ah, are you building with O= ? That might be the problem here, I think
I had to fix up that mess with the older driver in the past...
thanks,
greg k-h
next prev parent reply other threads:[~2021-07-30 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 13:53 build failure after merge of the staging tree Mark Brown
2021-07-30 14:02 ` Greg KH [this message]
2021-07-30 14:04 ` Mark Brown
2021-07-30 14:15 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2021-07-30 13:52 Mark Brown
2021-07-30 14:00 ` 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=YQQGgReGba/Ld40y@kroah.com \
--to=greg@kroah.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=phil@philpotter.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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