From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "Kumar, Udit" <u-kumar1@ti.com>
Cc: Bhavya Kapoor <b-kapoor@ti.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-can@vger.kernel.org, mailhol.vincent@wanadoo.fr,
rcsekar@samsung.com, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net, wg@grandegger.com,
vigneshr@ti.com
Subject: Re: [PATCH] net: can: Add support for aliases in CAN
Date: Fri, 12 Jan 2024 16:43:16 +0100 [thread overview]
Message-ID: <20240112-overreact-dwindling-2949267e8a02-mkl@pengutronix.de> (raw)
In-Reply-To: <8dee1738-0bde-48fb-bd0e-b8d06b609677@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
On 12.01.2024 20:53:32, Kumar, Udit wrote:
> Hi Marc
>
> On 1/2/2024 4:43 PM, Marc Kleine-Budde wrote:
> > On 02.01.2024 15:59:49, Bhavya Kapoor wrote:
> > > When multiple CAN's are present, then names that are getting assigned
> > > changes after every boot even after providing alias in the device tree.
> > > Thus, Add support for implementing CAN aliasing so that names or
> > > alias for CAN will now be provided from device tree.
> > NACK, please use udev or systemd-networkd to provide stable names for
> > CAN interfaces.
>
> Would you like to re-consider this NACK.
This is not a CAN device specific problem. If you want to change this,
talk/convince the networking people.
> From kernel side,
>
> IMO if aliasing is set in device tree then kernel should provide consistent
> baseline names.
>
> However, distributions may choose different or other stable naming,
>
> Also, if some distribution want to rely on kernel naming they still can do.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-01-12 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 10:29 [PATCH] net: can: Add support for aliases in CAN Bhavya Kapoor
2024-01-02 11:13 ` Marc Kleine-Budde
2024-01-12 15:23 ` Kumar, Udit
2024-01-12 15:43 ` Marc Kleine-Budde [this message]
2024-01-04 17:19 ` Simon Horman
2024-01-05 7:19 ` Bhavya Kapoor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240112-overreact-dwindling-2949267e8a02-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=b-kapoor@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rcsekar@samsung.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=wg@grandegger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).