From: Greg KH <gregkh@linux-foundation.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: davem@davemloft.net, sachin.kamat@linaro.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: staging/8821ae driver breaks allyes build in 3.16-rc*
Date: Sun, 20 Jul 2014 12:43:27 -0700 [thread overview]
Message-ID: <20140720194327.GA11230@kroah.com> (raw)
In-Reply-To: <20140720193821.GA12357@kroah.com>
On Sun, Jul 20, 2014 at 12:38:21PM -0700, Greg KH wrote:
> On Sun, Jul 20, 2014 at 12:25:11PM -0700, Greg KH wrote:
> > On Sun, Jul 20, 2014 at 09:05:23PM +0200, Andi Kleen wrote:
> > >
> > > Hi,
> > >
> > > I cannot build make allyesconfig in current Linus mainline, because
> > > drivers/staging/rtl8821ae has a lot of compile errors.
> >
> > allyesconfig should turn off the staging drivers, how did you turn it
> > on?
Ok, that's odd, I thought we didn't build staging drivers for
allyesconfig, but you are right, we do.
Anyway...
> > > Please fix it in some way, allyesconfig should build!
> >
> > It builds here for me, or at least I thought it did, let me go check...
> >
>
> I can't reproduce this here:
>
> $ make M=drivers/staging/rtl8821ae/ clean
> $ make -j16
> CHK include/config/kernel.release
> CHK include/generated/uapi/linux/version.h
> CHK include/generated/utsrelease.h
> CALL scripts/checksyscalls.sh
> CHK include/generated/compile.h
> CHK kernel/config_data.h
> LD drivers/staging/rtl8821ae/built-in.o
> CC [M] drivers/staging/rtl8821ae/btcoexist/halbtc8192e2ant.o
> CC [M] drivers/staging/rtl8821ae/btcoexist/halbtc8723b1ant.o
> CC [M] drivers/staging/rtl8821ae/btcoexist/halbtc8723b2ant.o
> CC [M] drivers/staging/rtl8821ae/btcoexist/halbtcoutsrc.o
> CC [M] drivers/staging/rtl8821ae/btcoexist/rtl_btc.o
> CC [M] drivers/staging/rtl8821ae/base.o
> CC [M] drivers/staging/rtl8821ae/rc.o
> CC [M] drivers/staging/rtl8821ae/debug.o
> CC [M] drivers/staging/rtl8821ae/regd.o
> CC [M] drivers/staging/rtl8821ae/efuse.o
> CC [M] drivers/staging/rtl8821ae/cam.o
> CC [M] drivers/staging/rtl8821ae/ps.o
> CC [M] drivers/staging/rtl8821ae/core.o
> CC [M] drivers/staging/rtl8821ae/stats.o
> CC [M] drivers/staging/rtl8821ae/pci.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/hw.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/table.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/sw.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/trx.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/led.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/fw.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/phy.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/dm.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/pwrseq.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/rf.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/pwrseqcmd.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/hal_btc.o
> CC [M] drivers/staging/rtl8821ae/rtl8821ae/hal_bt_coexist.o
> LD [M] drivers/staging/rtl8821ae/rtl8821ae.o
> CHK include/generated/uapi/linux/version.h
> Building modules, stage 2.
> Kernel: arch/x86/boot/bzImage is ready (#46)
> MODPOST 687 modules
> CC drivers/staging/rtl8821ae/rtl8821ae.mod.o
> LD [M] drivers/staging/rtl8821ae/rtl8821ae.ko
>
>
> Now that's with the "normal" config I build with, I'll go try a 'allyesconfig'
> now...
allyesconfig builds the staging directory just fine for me here, with
Linus's current tree:
$ git branch
* master d057190925d9 Merge branch 'locking-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
And gcc version:
$ gcc --version | head -n 1
gcc (GCC) 4.9.0 20140604 (prerelease)
Are you sure your tree is "clean" at the moment?
thanks,
greg k-h
next prev parent reply other threads:[~2014-07-20 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 19:05 staging/8821ae driver breaks allyes build in 3.16-rc* Andi Kleen
2014-07-20 19:25 ` Greg KH
2014-07-20 19:38 ` Greg KH
2014-07-20 19:43 ` Greg KH [this message]
2014-07-20 21:21 ` Andi Kleen
2014-07-20 21:59 ` Greg KH
2014-07-20 21:04 ` Andi Kleen
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=20140720194327.GA11230@kroah.com \
--to=gregkh@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.