From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, netdev <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v1] dt-bindings: net: ethernet-controller: document label property
Date: Wed, 9 Feb 2022 16:53:37 +0100 [thread overview]
Message-ID: <20220209155337.GA26024@pengutronix.de> (raw)
In-Reply-To: <CAL_Jsq+nWLrs0eAvNwV3suT4Xw+sLo6=yJhV9CyZXj+-xRE+Zg@mail.gmail.com>
On Wed, Feb 09, 2022 at 09:34:36AM -0600, Rob Herring wrote:
> On Wed, Feb 9, 2022 at 2:28 AM Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> >
> > "label" provides human readable name used on a box, board or schematic
> > to identify Ethernet port.
>
> Do you still need this?
Yes. No need to force label based name from kernel, but user space
should be able to use it to rename interface if needed or use it for
GUI. Otherwise user space will need to have date base of all boards to
provide this information.
Regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-02-09 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 8:28 [PATCH net-next v1] dt-bindings: net: ethernet-controller: document label property Oleksij Rempel
2022-02-09 15:34 ` Rob Herring
2022-02-09 15:53 ` Oleksij Rempel [this message]
2022-02-11 16:52 ` Rob Herring
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=20220209155337.GA26024@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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 NNTP newsgroup(s).