[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY2FFO11FD001BD9CFD92C94214501BB8E21B0@BY2FFO11FD001.protection.gbl>
Date: Mon, 9 Mar 2015 09:58:55 +0100
From: Michal Simek <michal.simek@...inx.com>
To: Marc Kleine-Budde <mkl@...gutronix.de>,
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>
Subject: Re: [PATCH] net: can: Enable xilinx driver for all ARCHs
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.
Or do you want me to change description to mention that this is for
ARM64 enabling?
Thanks,
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists