public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Michael Walle <michael@walle.cc>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	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, 28 Oct 2022 09:28:41 +0000	[thread overview]
Message-ID: <20221028092840.bprd37sn6nxwvzww@skbuf> (raw)
In-Reply-To: <2bad372ce42a06254c7767fd658d2a66@walle.cc>

On Fri, Oct 28, 2022 at 11:17:40AM +0200, Michael Walle wrote:
> >   alias:          dsa_tag-ocelot-8021q
> >   alias:          dsa_tag-20
> 
> I know that name clashes are not to be expected because one is a numerical id
> and the other is a string, but it might still make sense to have a different
> prefix so the user of modinfo can figure that out more easily.
> 
> Presuming that backwards compatibility is not an issue, maybe:
> dsa_tag-ocelot-8021q
> dsa_tag-id-20

Hm, it probably isn't an issue, but I'd like to hear from
Andrew/Florian/Vivien as well?

In the same note, "enum dsa_tag_protocol" isn't considered ABI either,
or in other words, we can reorder them, and DSA_TAG_PROTO_OCELOT_8021Q_VALUE
could become, say, 19 instead of 20 in a future kernel version, and that
would still be fine, because we would never load a module built for
kernel 6.1 in a 6.2 kernel?

> FWIW
> Tested-by: Michael Walle <michael@walle.cc> # on kontron-sl28 w/
> ocelot_8021q

Thanks for reporting the problem and for testing!

  reply	other threads:[~2022-10-28  9:28 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 [this message]
2022-10-30 21:22     ` Andrew Lunn
2022-11-11 22:53       ` Vladimir Oltean
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=20221028092840.bprd37sn6nxwvzww@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 \
    --cc=vivien.didelot@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox