From: Simon Horman <horms@kernel.org>
To: Larysa Zaremba <larysa.zaremba@intel.com>
Cc: intel-wired-lan@lists.osuosl.org,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Jiri Pirko <jiri@resnulli.us>,
Tatyana Nikolova <tatyana.e.nikolova@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Lee Trager <lee@trager.us>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Sridhar Samudrala <sridhar.samudrala@intel.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
Ahmed Zaki <ahmed.zaki@intel.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, "Karlsson,
Magnus" <magnus.karlsson@intel.com>,
Emil Tantilov <emil.s.tantilov@intel.com>,
Madhu Chittim <madhu.chittim@intel.com>,
Josh Hay <joshua.a.hay@intel.com>,
Milena Olech <milena.olech@intel.com>,
pavan.kumar.linga@intel.com, "Singhai,
Anjali" <anjali.singhai@intel.com>
Subject: Re: [PATCH iwl-next v3 00/15] Introduce iXD driver
Date: Mon, 12 May 2025 13:49:06 +0100 [thread overview]
Message-ID: <20250512124906.GA1417107@horms.kernel.org> (raw)
In-Reply-To: <20250509134319.66631-1-larysa.zaremba@intel.com>
On Fri, May 09, 2025 at 03:42:57PM +0200, Larysa Zaremba wrote:
> This patch series adds the iXD driver, which supports the Intel(R)
> Control Plane PCI Function on Intel E2100 and later IPUs and FNICs.
> It facilitates a centralized control over multiple IDPF PFs/VFs/SFs
> exposed by the same card. The reason for the separation is to be able
> to offload the control plane to the host different from where the data
> plane is running.
>
> This is the first phase in the release of this driver where we implement the
> initialization of the core PCI driver. Subsequent phases will implement
> advanced features like usage of idpf ethernet aux device, link management,
> NVM update via devlink, switchdev port representors, data and exception path,
> flow rule programming, etc.
Hi Larysa,
I am having a bit of trouble figuring out where to cleanly apply this
series to. Could you help me out?
next prev parent reply other threads:[~2025-05-12 12:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 13:42 Larysa Zaremba
2025-05-09 13:42 ` [PATCH iwl-next v3 01/15] virtchnl: create 'include/linux/intel' and move necessary header files Larysa Zaremba
2025-05-09 13:42 ` [PATCH iwl-next v3 02/15] virtchnl: introduce control plane version fields Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 03/15] libie: add PCI device initialization helpers to libie Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 04/15] libeth: allow to create fill queues without NAPI Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 05/15] libie: add control queue support Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 06/15] libie: add bookkeeping support for control queue messages Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 07/15] idpf: remove 'vport_params_reqd' field Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 08/15] idpf: refactor idpf to use libie_pci APIs Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 09/15] idpf: refactor idpf to use libie control queues Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 10/15] idpf: make mbx_task queueing and cancelling more consistent Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 11/15] idpf: print a debug message and bail in case of non-event ctlq message Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 12/15] ixd: add basic driver framework for Intel(R) Control Plane Function Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 13/15] ixd: add reset checks and initialize the mailbox Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 14/15] ixd: add the core initialization Larysa Zaremba
2025-05-09 13:43 ` [PATCH iwl-next v3 15/15] ixd: add devlink support Larysa Zaremba
2025-05-12 12:49 ` Simon Horman [this message]
2025-05-12 13:21 ` [PATCH iwl-next v3 00/15] Introduce iXD driver Larysa Zaremba
2025-05-12 18:41 ` Jacob Keller
2025-05-13 13:40 ` Simon Horman
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=20250512124906.GA1417107@horms.kernel.org \
--to=horms@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anjali.singhai@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=maddy@linux.ibm.com \
--cc=madhu.chittim@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=milena.olech@intel.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.kumar.linga@intel.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=tatyana.e.nikolova@intel.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
all inboxes | Powered by JetHome®