From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Andrew Lunn <andrew@lunn.ch>, Michael Walle <michael@walle.cc>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Heiko Thiery <heiko.thiery@gmail.com>
Subject: Re: [RFC PATCH net-next 0/3] Autoload DSA tagging driver when dynamically changing protocol
Date: Fri, 11 Nov 2022 22:53:42 +0000 [thread overview]
Message-ID: <20221111225341.2supj4ejtfohignw@skbuf> (raw)
In-Reply-To: <Y17rEVzO2w1RslrV@lunn.ch>
On Sun, Oct 30, 2022 at 10:22:25PM +0100, Andrew Lunn wrote:
> On Fri, Oct 28, 2022 at 09:28:41AM +0000, Vladimir Oltean wrote:
> > On Fri, Oct 28, 2022 at 11:17:40AM +0200, Michael Walle wrote:
> > > Presuming that backwards compatibility is not an issue, maybe:
> > > dsa_tag-id-20
>
> I don't think they are meant to be human readable.
>
> I do however wounder if they should be dsa_tag:ocelot-8021q,
> dsa_tag:20 ?
dsa_tag:20 or dsa_tag:id-20?
next prev parent reply other threads:[~2022-11-11 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 21:08 [RFC PATCH net-next 0/3] Autoload DSA tagging driver when dynamically changing protocol Vladimir Oltean
2022-10-27 21:08 ` [RFC PATCH net-next 1/3] net: dsa: fall back to default tagger if we can't load the one from DT Vladimir Oltean
2022-10-27 21:08 ` [RFC PATCH net-next 2/3] net: dsa: provide a second modalias to tag proto drivers based on their name Vladimir Oltean
2022-10-27 21:08 ` [RFC PATCH net-next 3/3] net: dsa: autoload tag driver module on tagging protocol change Vladimir Oltean
2022-10-28 9:17 ` [RFC PATCH net-next 0/3] Autoload DSA tagging driver when dynamically changing protocol Michael Walle
2022-10-28 9:28 ` Vladimir Oltean
2022-10-30 21:22 ` Andrew Lunn
2022-11-11 22:53 ` Vladimir Oltean [this message]
2022-11-11 22:54 ` Florian Fainelli
2022-11-11 23:03 ` Vladimir Oltean
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=20221111225341.2supj4ejtfohignw@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=kuba@kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.