[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1cc79929-ec7b-4d34-8cf3-25132da77e64@hartkopp.net>
Date: Fri, 28 Nov 2025 15:50:52 +0100
From: Oliver Hartkopp <socketcan@...tkopp.net>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: linux-can@...r.kernel.org, netdev@...r.kernel.org, davem@...emloft.net,
kuba@...nel.org, kernel@...gutronix.de, Vincent Mailhol <mailhol@...nel.org>
Subject: Re: [can-next] can: Kconfig: select CAN driver infrastructure by
default
On 28.11.25 15:43, Marc Kleine-Budde wrote:
> On 28.11.2025 11:08:03, Oliver Hartkopp wrote:
>> The CAN bus support enabled with CONFIG_CAN provides a socket-based
>> access to CAN interfaces. With the introduction of the latest CAN protocol
>> CAN XL additional configuration status information needs to be exposed to
>> the network layer than formerly provided by standard Linux network drivers.
>>
>> This requires the CAN driver infrastructure to be selected by default.
>> As the CAN network layer can only operate on CAN interfaces anyway all
>> distributions and common default configs enable at least one CAN driver.
>>
>> So selecting CONFIG_CAN_DEV when CONFIG_CAN is selected by the user has
>> no effect on established configurations but solves potential build issues
>> when CONFIG_CAN[_XXX]=y is set together with CANFIG_CAN_DEV=m
>>
>> Fixes: 1a620a723853 ("can: raw: instantly reject unsupported CAN frames")
>> Reported-by: Vincent Mailhol <mailhol@...nel.org>
>> Suggested-by: Marc Kleine-Budde <mkl@...gutronix.de>
>> Signed-off-by: Oliver Hartkopp <socketcan@...tkopp.net>
>
> I think we take this, at least for now. But I'll remove my Suggested-by,
> which was a leftover from v3.
Sure?
I remember you suggested some Kconfig magic :-D
Ok, this patch has not so much magic inside ... but it is tested!
Best regards,
Oliver
Powered by blists - more mailing lists