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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C8270C433EF for ; Mon, 4 Oct 2021 07:38:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AFEEB6117A for ; Mon, 4 Oct 2021 07:38:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230036AbhJDHkc (ORCPT ); Mon, 4 Oct 2021 03:40:32 -0400 Received: from jabberwock.ucw.cz ([46.255.230.98]:36646 "EHLO jabberwock.ucw.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230010AbhJDHkb (ORCPT ); Mon, 4 Oct 2021 03:40:31 -0400 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id 0E62A1C0B76; Mon, 4 Oct 2021 09:38:42 +0200 (CEST) Date: Mon, 4 Oct 2021 09:38:41 +0200 From: Pavel Machek To: Greg Kroah-Hartman Cc: Marek =?iso-8859-1?Q?Beh=FAn?= , Andrew Lunn , "linux-leds@vger.kernel.org" , netdev@vger.kernel.org, Jacek Anaszewski , linux-kernel@vger.kernel.org Subject: Re: are device names part of sysfs ABI? (was Re: devicename part of LEDs under ethernet MAC / PHY) Message-ID: <20211004073841.GA20163@amd> References: <20211001133057.5287f150@thinkpad> <20211001144053.3952474a@thinkpad> <20211003225338.76092ec3@thinkpad> <20211004090438.588a8a89@thinkpad> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Precedence: bulk List-ID: X-Mailing-List: linux-leds@vger.kernel.org --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > > > Are device names (as returned by dev_name() function) also part of > > > > sysfs ABI? Should these names be stable across reboots / kernel > > > > upgrades? =20 > > >=20 > > > Stable in what exact way? > >=20 > > Example: > > - Board has an ethernet PHYs that is described in DT, and therefore > > has stable sysfs path (derived from DT path), something like > > /sys/devices/.../mdio_bus/f1072004.mdio-mii/f1072004.mdio-mii:01 >=20 > None of the numbers there are "stable", right? At least f1072004 part is stable (and probably whole path). DT has advantages here, and we should provide stable paths when we can. Best regards, Pavel --=20 http://www.livejournal.com/~pavelmachek --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAmFar4AACgkQMOfwapXb+vK1sgCgtfhhY9twaL0KgQm9FOL3VLwb xdQAoI9WQF6v3AbSYLUg1EZELXzIEFLV =UMpO -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3--