From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: linux-next: Tree for May 26 (staging/rtl8192ee)
Date: Mon, 26 May 2014 10:47:26 -0700 [thread overview]
Message-ID: <53837E2E.8060605@infradead.org> (raw)
In-Reply-To: <20140526193819.2ba7bc07@canb.auug.org.au>
On 05/26/2014 02:38 AM, Stephen Rothwell wrote:
> Hi all,
>
> The powerpc allyesconfig is again broken more than usual.
>
> Changes since 20140523:
>
on x86_64:
when CONFIG_PCI is not enabled:
CC drivers/staging/rtl8192ee/pci.o
../drivers/staging/rtl8192ee/pci.c: In function 'rtl_pci_intr_mode_msi':
../drivers/staging/rtl8192ee/pci.c:2045:2: error: implicit declaration of function 'pci_enable_msi' [-Werror=implicit-function-declaration]
../drivers/staging/rtl8192ee/pci.c:2052:3: error: implicit declaration of function 'pci_disable_msi' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[4]: [drivers/staging/rtl8192ee/pci.o] Error 1 (ignored)
Larry, please check this but be suspicious of it at the same time.
It was generated by having gcc ignore errors and keep going, but
I expect that there is a problem here.
thanks,
--
~Randy
prev parent reply other threads:[~2014-05-26 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 9:38 linux-next: Tree for May 26 Stephen Rothwell
2014-05-26 9:38 ` Stephen Rothwell
2014-05-26 17:41 ` linux-next: Tree for May 26 (syscalls is85/ia32 on x86_64) Randy Dunlap
2014-05-26 17:47 ` Randy Dunlap [this message]
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=53837E2E.8060605@infradead.org \
--to=rdunlap@infradead.org \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.