From: Jakub Kicinski <kuba@kernel.org>
To: Dave Ertman <david.m.ertman@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
daniel.machon@microchip.com, simon.horman@corigine.com,
bcreeley@amd.com, anthony.l.nguyen@intel.com
Subject: Re: [PATCH iwl-next v6 00/10] Implement support for SRIOV + LAG
Date: Tue, 20 Jun 2023 19:19:07 -0700 [thread overview]
Message-ID: <20230620191907.3a812399@kernel.org> (raw)
In-Reply-To: <20230620221854.848606-1-david.m.ertman@intel.com>
On Tue, 20 Jun 2023 15:18:44 -0700 Dave Ertman wrote:
> Implement support for SRIOV VF's on interfaces that are in an
> aggregate interface.
>
> The first interface added into the aggregate will be flagged as
> the primary interface, and this primary interface will be
> responsible for managing the VF's resources. VF's created on the
> primary are the only VFs that will be supported on the aggregate.
> Only Active-Backup mode will be supported and only aggregates whose
> primary interface is in switchdev mode will be supported.
If you're CCing netdev you need to obey netdev rules:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#resending-after-review
You have sent two version of this today (and there weren't even
any replies).
next prev parent reply other threads:[~2023-06-21 2:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 22:18 [PATCH iwl-next v6 00/10] Implement support for SRIOV + LAG Dave Ertman
2023-06-20 22:18 ` [PATCH iwl-next v6 01/10] ice: Correctly initialize queue context values Dave Ertman
2023-07-07 11:53 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-20 22:18 ` [PATCH iwl-next v6 02/10] ice: Add driver support for firmware changes for LAG Dave Ertman
2023-07-07 11:54 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-20 22:18 ` [PATCH iwl-next v6 03/10] ice: changes to the interface with the HW and FW for SRIOV_VF+LAG Dave Ertman
2023-07-07 11:57 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-20 22:18 ` [PATCH iwl-next v6 04/10] ice: implement lag netdev event handler Dave Ertman
2023-07-07 11:58 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-20 22:18 ` [PATCH iwl-next v6 05/10] ice: process events created by " Dave Ertman
2023-07-07 11:59 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-20 22:18 ` [PATCH iwl-next v6 06/10] ice: Flesh out implementation of support for SRIOV on bonded interface Dave Ertman
2023-07-07 12:00 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-20 22:18 ` [PATCH iwl-next v6 07/10] ice: support non-standard teardown of bond interface Dave Ertman
2023-07-07 12:00 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-20 22:18 ` [PATCH iwl-next v6 08/10] ice: enforce interface eligibility and add messaging for SRIOV LAG Dave Ertman
2023-07-07 12:01 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-20 22:18 ` [PATCH iwl-next v6 09/10] ice: enforce no DCB config changing when in bond Dave Ertman
2023-07-07 12:02 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-20 22:18 ` [PATCH iwl-next v6 10/10] ice: update reset path for SRIOV LAG support Dave Ertman
2023-07-07 12:02 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-21 2:19 ` Jakub Kicinski [this message]
2023-06-21 14:39 ` [PATCH iwl-next v6 00/10] Implement support for SRIOV + LAG Ertman, David M
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=20230620191907.3a812399@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=bcreeley@amd.com \
--cc=daniel.machon@microchip.com \
--cc=david.m.ertman@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@corigine.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).