Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 18 Jul 2022 12:15:07 +0200
From:   Marc Kleine-Budde <mkl@pengutronix.de>
To:     Oliver Hartkopp <socketcan@hartkopp.net>
Cc:     Max Staudt <max@enpas.org>,
        Dario Binacchi <dario.binacchi@amarulasolutions.com>,
        linux-kernel@vger.kernel.org,
        Jeroen Hofstee <jhofstee@victronenergy.com>,
        michael@amarulasolutions.com,
        Amarula patchwork <linux-amarula@amarulasolutions.com>,
        "David S. Miller" <davem@davemloft.net>,
        Eric Dumazet <edumazet@google.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Jakub Kicinski <kuba@kernel.org>,
        Jiri Slaby <jirislaby@kernel.org>,
        Paolo Abeni <pabeni@redhat.com>,
        Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
        Wolfgang Grandegger <wg@grandegger.com>,
        linux-can@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC PATCH 2/5] can: slcan: remove legacy infrastructure
Message-ID: <20220718101507.eioy2bdcmjkgtacz@pengutronix.de>
References: <20220716170007.2020037-1-dario.binacchi@amarulasolutions.com>
 <20220716170007.2020037-3-dario.binacchi@amarulasolutions.com>
 <20220717233842.1451e349.max@enpas.org>
 <6faf29c7-3e9d-bc21-9eac-710f901085d8@hartkopp.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="gbbsrwdp7reehx4n"
Content-Disposition: inline
In-Reply-To: <6faf29c7-3e9d-bc21-9eac-710f901085d8@hartkopp.net>
Precedence: bulk


--gbbsrwdp7reehx4n
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 18.07.2022 08:57:21, Oliver Hartkopp wrote:
> > What do the maintainers think of dropping the old "slcan" name, and
> > just allowing this to be a normal canX device? These patches do bring
> > it closer to that, after all. In this case, this name string magic
> > could be dropped altogether.
> >=20
>=20
> I'm fine with it in general. But we have to take into account that there
> might be existing setups that still might use the slcan_attach or slcand
> mechanic which will likely break after the kernel update.
>=20
> But in the end the slcan0 shows up everywhere - even in log files, etc.
>=20
> So we really should name it canX. When people really get in trouble with =
it,
> they can rename the network interface name with the 'ip' tool ...

Don't break user space! If you don't like slcanX use udev to give it a
proper name.

regards,
Marc

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

--gbbsrwdp7reehx4n
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEBsvAIBsPu6mG7thcrX5LkNig010FAmLVMqkACgkQrX5LkNig
011fVggAhIqvpyjYuqNRGmzUXsKCFCmmzPv58yhfyNhblDiwov4AeO0dmDEgDA9R
DbWo9aqPKF/KydxOEe+qYVutKrCBkXmZiZepKrVwTFMswcqMxngMytzh/n9eO126
dNx5xSuPVTP6bEC4U9Y9XXxVguv5UBVTf6UHsIQGErkltdqiITq1QKhYK3hogzkk
vMfNmWeMrXtFzCCLA6ShHL/7HmCsSvKsD5RD9Tm6I5IVcc5a1iaJPZ6xaYY5FsBc
tJDGfBZdxEIEi2d4qQix88fLYWtFoBI4pscyWqIvudmuio0ZUJbcE1tNVarP4hya
XSjg8Lxv6XeKQjymjbBUOjYDPmQgAg==
=y6Hg
-----END PGP SIGNATURE-----

--gbbsrwdp7reehx4n--