[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG88wWb+vN+3RFE8KKHY_W9ggBefhFAMZfX+FRNS=8ry_GUOvA@mail.gmail.com>
Date: Wed, 21 Jun 2023 13:19:50 -0700
From: David Decotigny <ddecotig@...gle.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Jakub Kicinski <kuba@...nel.org>, "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,
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
For information, we have tested this driver as is proposed in its
current form, and merging it into 6.5 would work best, provided that
the follow-up improvements can be provided in a later set of
submissions.
--
David Decotigny -- Platforms, US SVL MAT3 -- go/balance/decot
On Wed, Jun 21, 2023 at 12:45 PM Andrew Lunn <andrew@...n.ch> wrote:
>
> On Wed, Jun 21, 2023 at 12:28:53PM -0700, Jakub Kicinski wrote:
> > On Wed, 21 Jun 2023 12:13:06 -0700 Linga, Pavan Kumar wrote:
> > > Thanks for the feedback. Given the timing and type of changes requested
> > > for the patches, would it be possible to accept this patch series (v3)
> > > in its current form, as we continue to develop and address all the
> > > feedback in followup patches?
> >
> > 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.
>
> 2.5. Staging trees
>
> The kernel source tree contains the drivers/staging/ directory,
> where many sub-directories for drivers or filesystems that are on
> their way to being added to the kernel tree live. They remain in
> drivers/staging while they still need more work; once complete,
> they can be moved into the kernel proper. This is a way to keep
> track of drivers that aren't up to Linux kernel coding or quality
> standards, but people may want to use them and track development.
>
> Andrew
Powered by blists - more mailing lists