From: Jakub Kicinski <kuba@kernel.org>
To: Emil Tantilov <emil.s.tantilov@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
joshua.a.hay@intel.com, sridhar.samudrala@intel.com,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
willemb@google.com, decot@google.com, pabeni@redhat.com,
edumazet@google.com, davem@davemloft.net, alan.brady@intel.com,
madhu.chittim@intel.com, phani.r.burra@intel.com,
shailendra.bhatnagar@intel.com, pavan.kumar.linga@intel.com,
shannon.nelson@amd.com, simon.horman@corigine.com,
leon@kernel.org
Subject: Re: [net-next v3 00/15] Introduce Intel IDPF driver
Date: Wed, 26 Apr 2023 19:46:23 -0700 [thread overview]
Message-ID: <20230426194623.5b922067@kernel.org> (raw)
In-Reply-To: <20230427020917.12029-1-emil.s.tantilov@intel.com>
On Wed, 26 Apr 2023 19:09:02 -0700 Emil Tantilov wrote:
> This patch series introduces the Intel Infrastructure Data Path Function
> (IDPF) driver. It is used for both physical and virtual functions. Except
> for some of the device operations the rest of the functionality is the
> same for both PF and VF. IDPF uses virtchnl version2 opcodes and
> structures defined in the virtchnl2 header file which helps the driver
> to learn the capabilities and register offsets from the device
> Control Plane (CP) instead of assuming the default values.
This is not the right time to post patches, see below.
Please have Tony/Jesse take over posting of this code to the list
going forward. Intel has a history of putting upstream training on
the community, we're not going thru this again.
## Form letter - net-next-closed
The merge window for v6.3 has begun and therefore net-next is closed
for new drivers, features, code refactoring and optimizations.
We are currently accepting bug fixes only.
Please repost when net-next reopens after May 8th.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
next prev parent reply other threads:[~2023-04-27 2:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 2:09 [net-next v3 00/15] Introduce Intel IDPF driver Emil Tantilov
2023-04-27 2:09 ` [net-next v3 01/15] virtchnl: add virtchnl version 2 ops Emil Tantilov
2023-04-27 22:04 ` Shannon Nelson
2023-04-28 23:10 ` Tantilov, Emil S
2023-04-27 2:09 ` [net-next v3 02/15] idpf: add module register and probe functionality Emil Tantilov
2023-04-27 23:24 ` Shannon Nelson
2023-04-28 23:05 ` Tantilov, Emil S
2023-04-27 2:09 ` [net-next v3 03/15] idpf: add controlq init and reset checks Emil Tantilov
2023-04-28 17:16 ` Shannon Nelson
2023-04-28 22:38 ` Tantilov, Emil S
2023-04-27 2:09 ` [net-next v3 04/15] idpf: add core init and interrupt request Emil Tantilov
2023-04-28 19:50 ` Shannon Nelson
2023-04-28 21:17 ` Tantilov, Emil S
2023-04-27 2:09 ` [net-next v3 05/15] idpf: add create vport and netdev configuration Emil Tantilov
2023-04-27 2:09 ` [net-next v3 06/15] idpf: continue expanding init task Emil Tantilov
2023-04-27 2:09 ` [net-next v3 07/15] idpf: configure resources for TX queues Emil Tantilov
2023-04-27 2:09 ` [net-next v3 08/15] idpf: configure resources for RX queues Emil Tantilov
2023-04-27 2:09 ` [net-next v3 09/15] idpf: initialize interrupts and enable vport Emil Tantilov
2023-04-27 2:09 ` [net-next v3 10/15] idpf: add splitq start_xmit Emil Tantilov
2023-04-27 2:09 ` [net-next v3 11/15] idpf: add TX splitq napi poll support Emil Tantilov
2023-04-27 2:09 ` [net-next v3 12/15] idpf: add RX " Emil Tantilov
2023-04-27 2:09 ` [net-next v3 13/15] idpf: add singleq start_xmit and napi poll Emil Tantilov
2023-04-27 2:09 ` [net-next v3 14/15] idpf: add ethtool callbacks Emil Tantilov
2023-04-27 2:09 ` [net-next v3 15/15] idpf: configure SRIOV and add other ndo_ops Emil Tantilov
2023-04-27 2:46 ` Jakub Kicinski [this message]
2023-04-27 2:55 ` [net-next v3 00/15] Introduce Intel IDPF driver Tantilov, Emil S
2023-04-27 3:29 ` Jakub Kicinski
2023-04-27 22:23 ` Jesse Brandeburg
2023-05-03 2:20 ` Jakub Kicinski
2023-05-03 16:24 ` Jesse Brandeburg
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=20230426194623.5b922067@kernel.org \
--to=kuba@kernel.org \
--cc=alan.brady@intel.com \
--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=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=joshua.a.hay@intel.com \
--cc=leon@kernel.org \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.kumar.linga@intel.com \
--cc=phani.r.burra@intel.com \
--cc=shailendra.bhatnagar@intel.com \
--cc=shannon.nelson@amd.com \
--cc=simon.horman@corigine.com \
--cc=sridhar.samudrala@intel.com \
--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).