[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D0F914F.2050908@oracle.com>
Date: Mon, 20 Dec 2010 09:24:31 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Peter Hüwe <PeterHuewe@....de>
CC: sedat.dilek@...il.com, Stephen Rothwell <sfr@...b.auug.org.au>,
Corentin Chary <corentin.chary@...il.com>,
Matthew Garrett <mjg@...hat.com>,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
John Linville <linville@...driver.com>
Subject: Re: [PATCH] platform/x86: Fix recursive Kconfig dependency
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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists