lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 9 Oct 2014 19:15:32 +0200
From:	Arend van Spriel <arend@...adcom.com>
To:	Rafał Miłecki <zajec5@...il.com>
CC:	Guenter Roeck <linux@...ck-us.net>,
	"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

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?

btw. the OF_ADDRESS dependency was introduced by commit "bcma: get IRQ 
numbers from dt".

Regards,
Arend

> Won't this make bcma im-POSSIBLE on MIPS? And maybe x86(_64), or at
> least add an unneeded dependency? I think we should somehow limit this
> to BCM5301X arch.
> --
> 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/

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ