lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221111230337.7ctkuwmlerdntbnu@skbuf>
Date:   Fri, 11 Nov 2022 23:03:38 +0000
From:   Vladimir Oltean <vladimir.oltean@....com>
To:     Florian Fainelli <f.fainelli@...il.com>
CC:     Andrew Lunn <andrew@...n.ch>, Michael Walle <michael@...le.cc>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Heiko Thiery <heiko.thiery@...il.com>
Subject: Re: [RFC PATCH net-next 0/3] Autoload DSA tagging driver when
 dynamically changing protocol

On Fri, Nov 11, 2022 at 02:54:18PM -0800, Florian Fainelli wrote:
> On 11/11/22 14:53, Vladimir Oltean wrote:
> > 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?
> 
> The latter IMHO would be more explicit.

Okay, thanks.

Powered by blists - more mailing lists