[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 10 Oct 2014 11:24:53 +1100
From: Julian Calaby <julian.calaby@...il.com>
To: Guenter Roeck <linux@...ck-us.net>,
sparclinux <sparclinux@...r.kernel.org>
Cc: Arend van Spriel <arend@...adcom.com>,
Rafał Miłecki <zajec5@...il.com>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Hauke Mehrtens <hauke@...ke-m.de>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH] bcma: Add dependency on OF_ADDRESS
Hi,
On Fri, Oct 10, 2014 at 4:21 AM, Guenter Roeck <linux@...ck-us.net> wrote:
> On Thu, Oct 09, 2014 at 07:15:32PM +0200, Arend van Spriel wrote:
>> On 10/09/14 18:54, Rafał Miłecki wrote:
>> >On 9 October 2014 18:41, Guenter Roeck<linux@...ck-us.net> wrote:
>> >>Commit 2101e533f41a ("bcma: register bcma as device tree driver")
>> >>introduces a hard dependency on OF_ADDRESS into the bcma driver.
>> >>OF_ADDRESS is specifically disabled for the sparc architecture.
>> >>This results in the following error when building sparc64:allmodconfig.
>>
>> Does this mean on sparc (using allmodconfig) you will get CONFIG_OF
>> and !CONFIG_OF_ADDRESS? Does that makes sense?
>>
>
> You tell me. From drivers/of/Kconfig:
>
> config OF_ADDRESS
> def_bool y
> depends on !SPARC
> select OF_ADDRESS_PCI if PCI
>
> Presumably there is a reason to disable OF_ADDRESS for sparc.
Why not ask the sparclinux list? (CC'd)
Thanks,
--
Julian Calaby
Email: julian.calaby@...il.com
Profile: http://www.google.com/profiles/julian.calaby/
--
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