From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: sedat.dilek@gmail.com, Stephen Rothwell <sfr@canb.auug.org.au>,
Corentin Chary <corentin.chary@gmail.com>,
Matthew Garrett <mjg@redhat.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] platform/x86: Fix recursive Kconfig dependency
Date: Mon, 20 Dec 2010 09:24:31 -0800 [thread overview]
Message-ID: <4D0F914F.2050908@oracle.com> (raw)
In-Reply-To: <201012201809.41269.PeterHuewe@gmx.de>
On 12/20/10 09:09, Peter Hüwe wrote:
> Am Montag 20 Dezember 2010, 15:46:02 schrieb Sedat Dilek:
>>> Added Stephen Rothwell on CC, maybe he can apply it directly to
>>> linux-next ;)
>>>
>>> Peter
>>
>> I do not think this will happen for a "as-warning-classified" patch.
>
> On arm and avr32 it is not only a warning but an error instead!
>
> -> so the patch fixes an error / build failure which imho is quite an
> important issue.
>
> You can see the errors in Ellerman's build farm.
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/3652816/
> http://kisskb.ellerman.id.au/kisskb/buildresult/3664077/
> http://kisskb.ellerman.id.au/kisskb/buildresult/3652972/
> http://kisskb.ellerman.id.au/kisskb/buildresult/3664113/
>
> As it is an error for arm and avr32 maybe it should go through their trees
> instead?
It's a kconfig "error" on x86 also, but it does not stop the .config file
from being generated. It needs to be fixed, but it's not deadly.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
desserts: http://www.xenotime.net/linux/recipes/
prev parent reply other threads:[~2010-12-20 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 23:29 [PATCH] platform/x86: Fix recursive Kconfig dependency Peter Huewe
2010-12-15 20:35 ` Peter Hüwe
2010-12-15 20:49 ` Corentin Chary
2010-12-15 20:51 ` Randy Dunlap
2010-12-15 21:14 ` Peter Hüwe
2010-12-17 11:30 ` Sedat Dilek
2010-12-19 19:00 ` Peter Hüwe
2010-12-20 14:46 ` Sedat Dilek
2010-12-20 17:09 ` Peter Hüwe
2010-12-20 17:24 ` 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=4D0F914F.2050908@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=PeterHuewe@gmx.de \
--cc=corentin.chary@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox