From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 24EEAC43334 for ; Mon, 18 Jul 2022 10:15:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233988AbiGRKP1 (ORCPT ); Mon, 18 Jul 2022 06:15:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59024 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233947AbiGRKP0 (ORCPT ); Mon, 18 Jul 2022 06:15:26 -0400 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A816611441 for ; Mon, 18 Jul 2022 03:15:25 -0700 (PDT) Received: from gallifrey.ext.pengutronix.de ([2001:67c:670:201:5054:ff:fe8d:eefb] helo=bjornoya.blackshift.org) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oDNmS-00052z-6f; Mon, 18 Jul 2022 12:15:12 +0200 Received: from pengutronix.de (unknown [IPv6:2a01:4f8:1c1c:29e9:22:41ff:fe00:1400]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: mkl-all@blackshift.org) by smtp.blackshift.org (Postfix) with ESMTPSA id 770CFB2F94; Mon, 18 Jul 2022 10:15:08 +0000 (UTC) Date: Mon, 18 Jul 2022 12:15:07 +0200 From: Marc Kleine-Budde To: Oliver Hartkopp Cc: Max Staudt , Dario Binacchi , linux-kernel@vger.kernel.org, Jeroen Hofstee , michael@amarulasolutions.com, Amarula patchwork , "David S. Miller" , Eric Dumazet , Greg Kroah-Hartman , Jakub Kicinski , Jiri Slaby , Paolo Abeni , Vincent Mailhol , Wolfgang Grandegger , 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> X-SA-Exim-Connect-IP: 2001:67c:670:201:5054:ff:fe8d:eefb X-SA-Exim-Mail-From: mkl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: netdev@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org --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--