From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Linga, Pavan Kumar" <pavan.kumar.linga@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
netdev@vger.kernel.org, emil.s.tantilov@intel.com,
jesse.brandeburg@intel.com, sridhar.samudrala@intel.com,
shiraz.saleem@intel.com, sindhu.devale@intel.com,
willemb@google.com, decot@google.com, leon@kernel.org,
mst@redhat.com, simon.horman@corigine.com,
shannon.nelson@amd.com, stephen@networkplumber.org
Subject: Re: [PATCH net-next v3 00/15][pull request] Introduce Intel IDPF driver
Date: Wed, 21 Jun 2023 13:46:44 -0700 [thread overview]
Message-ID: <20230621134644.79ebe113@kernel.org> (raw)
In-Reply-To: <03819ef3-8008-43e9-8618-f37f5bc5160b@lunn.ch>
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.
prev parent reply other threads:[~2023-06-21 20:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 23:13 [PATCH net-next v3 00/15][pull request] Introduce Intel IDPF driver Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 01/15] virtchnl: add virtchnl version 2 ops Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 02/15] idpf: add module register and probe functionality Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 03/15] idpf: add controlq init and reset checks Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 04/15] idpf: add core init and interrupt request Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 05/15] idpf: add create vport and netdev configuration Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 06/15] idpf: add ptypes and MAC filter support Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 07/15] idpf: configure resources for TX queues Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 08/15] idpf: configure resources for RX queues Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 09/15] idpf: initialize interrupts and enable vport Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 10/15] idpf: add splitq start_xmit Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 11/15] idpf: add TX splitq napi poll support Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 12/15] idpf: add RX " Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 13/15] idpf: add singleq start_xmit and napi poll Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 14/15] idpf: add ethtool callbacks Tony Nguyen
2023-06-16 23:13 ` [PATCH net-next v3 15/15] idpf: configure SRIOV and add other ndo_ops Tony Nguyen
2023-06-17 6:56 ` [PATCH net-next v3 00/15][pull request] Introduce Intel IDPF driver Jakub Kicinski
2023-06-21 19:13 ` Linga, Pavan Kumar
2023-06-21 19:28 ` Jakub Kicinski
2023-06-21 19:44 ` Andrew Lunn
2023-06-21 20:19 ` David Decotigny
2023-06-21 20:46 ` Jakub Kicinski [this message]
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=20230621134644.79ebe113@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=leon@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.kumar.linga@intel.com \
--cc=shannon.nelson@amd.com \
--cc=shiraz.saleem@intel.com \
--cc=simon.horman@corigine.com \
--cc=sindhu.devale@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=stephen@networkplumber.org \
--cc=willemb@google.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;
as well as URLs for NNTP newsgroup(s).