[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230621134644.79ebe113@kernel.org>
Date: Wed, 21 Jun 2023 13:46:44 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: "Linga, Pavan Kumar" <pavan.kumar.linga@...el.com>, Tony Nguyen
<anthony.l.nguyen@...el.com>, davem@...emloft.net, pabeni@...hat.com,
edumazet@...gle.com, netdev@...r.kernel.org, emil.s.tantilov@...el.com,
jesse.brandeburg@...el.com, sridhar.samudrala@...el.com,
shiraz.saleem@...el.com, sindhu.devale@...el.com, willemb@...gle.com,
decot@...gle.com, leon@...nel.org, mst@...hat.com,
simon.horman@...igine.com, shannon.nelson@....com,
stephen@...workplumber.org
Subject: Re: [PATCH net-next v3 00/15][pull request] Introduce Intel IDPF
driver
On Wed, 21 Jun 2023 21:44:55 +0200 Andrew Lunn wrote:
> > I think you're asking to be accepted in a Linux-Staging kind of a way?
>
> Or maybe real staging, driver/staging ? Add a TODO and GregKH might
> accept it.
Ah, I was half joking, that always backfires.
We merge a driver of this size in every release cycle. Nobody else
needed training wheels to upstream an Ethernet driver for as long
as I remember. It'd be best if Pavan left negotiations on how to get
the driver merged to people with more upstream experience.
Powered by blists - more mailing lists