[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YyyyphcLn8UQse2F@unreal>
Date: Thu, 22 Sep 2022 22:08:22 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Simon Horman <simon.horman@...igine.com>,
David Miller <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
oss-drivers@...igine.com, Diana Wang <na.wang@...igine.com>,
Peng Zhang <peng.zhang@...igine.com>,
Michael Chan <michael.chan@...adcom.com>,
Andy Gospodarek <andy@...yhouse.net>,
Gal Pressman <gal@...dia.com>,
Saeed Mahameed <saeed@...nel.org>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
Tony Nguyen <anthony.l.nguyen@...el.com>,
Edward Cree <ecree.xilinx@...il.com>,
Vladimir Oltean <vladimir.oltean@....com>,
Andrew Lunn <andrew@...n.ch>
Subject: Re: driver uABI review list? (was: Re: [PATCH/RFC net-next 0/3] nfp:
support VF multi-queues configuration)
On Thu, Sep 22, 2022 at 09:14:14AM -0700, Jakub Kicinski wrote:
> On Thu, 22 Sep 2022 19:04:19 +0300 Leon Romanovsky wrote:
> > > Would it be helpful for participation if we had a separate mailing
> > > list for discussing driver uAPI introduction which would hopefully
> > > be lower traffic?
> >
> > Please don't. It will cause to an opposite situation where UAPI
> > discussions will be hidden from most people.
>
> Oh, it'd just be an additional list, the patches would still need
> to CC netdev.
First, there is already such ML: https://lore.kernel.org/linux-api/
Second, you disconnect discussion from actual patches and this can
cause to repeating of same arguments while reviewing patches.
>
> > IMHO, every net vendor should be registered to netdev mailing list
> > and read, review and participate.
>
> Alright, so we got two no votes so far.
Powered by blists - more mailing lists