linux-kernel - Re: [PATCH] net: can: Enable xilinx driver for all ARCHs

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:	Mon, 09 Mar 2015 10:13:00 +0100
From:	Marc Kleine-Budde <mkl@...gutronix.de>
To:	Michal Simek <michal.simek@...inx.com>,
	linux-kernel@...r.kernel.org, monstr@...str.eu
CC:	Wolfgang Grandegger <wg@...ndegger.com>, linux-can@...r.kernel.org,
	netdev@...r.kernel.org, Jean Delvare <jdelvare@...e.de>
Subject: Re: [PATCH] net: can: Enable xilinx driver for all ARCHs

On 03/09/2015 09:58 AM, Michal Simek wrote:
> On 03/09/2015 09:50 AM, Marc Kleine-Budde wrote:
>> On 03/09/2015 09:48 AM, Michal Simek wrote:
>>> Remove Kconfig dependency and enable driver for
>>> all ARCHs.
>>>
>>> Signed-off-by: Michal Simek <michal.simek@...inx.com>
>>> Acked-by: Sören Brinkmann <soren.brinkmann@...inx.com>
>>> ---
>>>
>>> Test for all archs done by Kbuild test robot without any problem.
>>> ---
>>>  drivers/net/can/Kconfig | 1 -
>>>  1 file changed, 1 deletion(-)
>>>
>>> diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig
>>> index 98d73aab52fe..f690c3fb3088 100644
>>> --- a/drivers/net/can/Kconfig
>>> +++ b/drivers/net/can/Kconfig
>>> @@ -131,7 +131,6 @@ config CAN_RCAR
>>>  
>>>  config CAN_XILINXCAN
>>>  	tristate "Xilinx CAN"
>>> -	depends on ARCH_ZYNQ || MICROBLAZE || COMPILE_TEST
>>
>> I think that's what COMPILE_TEST ist for?
> 
> For compilation yes but not for enabling. Currently this driver
> can be also used on ARM64 that's why people suggesting directly
> to remove dependency on arch and then COMPILE_TEST can be removed
> too.

In the past (May 2014) I had people complaining that certain ARM SoC
specific drivers are enabled on ARM in general, not just on that SoC. As
I'm not following arm64 in detail, has the notion of using depends on
ARCH changes since then?

> Or do you want me to change description to mention that this is for
> ARM64 enabling?

Given this is consensus, a remark to ARM64 would be appreciated. :)

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)