[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e361c02b-fddc-4b80-9ae2-ee3f2b69f69a@lunn.ch>
Date: Wed, 21 May 2025 14:23:37 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Geert Uytterhoeven <geert+renesas@...der.be>
Cc: Oliver Hartkopp <socketcan@...tkopp.net>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Jonathan Corbet <corbet@....net>,
Wolfgang Grandegger <wg@...ndegger.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, linux-can@...r.kernel.org,
netdev@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH] documentation: networking: can: Document
alloc_candev_mqs()
On Wed, May 21, 2025 at 11:51:21AM +0200, Geert Uytterhoeven wrote:
> Since the introduction of alloc_candev_mqs() and friends, there is no
> longer a need to allocate a generic network device and perform explicit
> CAN-specific setup. Remove the code showing this setup, and document
> alloc_candev_mqs() instead.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> ---
> Dunno if this deserves
> Fixes: 39549eef3587f1c1 ("can: CAN Network device driver and Netlink interface")
Documentation often does get added to net and back ported. It is not
going to break anything, and there are developers who work on the last
LTS rather than net-next.
Andrew
Powered by blists - more mailing lists