From: "Pucha, HimasekharX Reddy" <himasekharx.reddy.pucha@intel.com>
To: "Ertman, David M" <david.m.ertman@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>
Subject: RE: [Intel-wired-lan] [PATCH iwl-net] ice: Add check for lport extraction to LAG init
Date: Fri, 9 Feb 2024 11:08:09 +0000 [thread overview]
Message-ID: <CYYPR11MB8429B8B327BD807EE4761671BD4B2@CYYPR11MB8429.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240119211517.127142-1-david.m.ertman@intel.com>
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of Dave Ertman
> Sent: Saturday, January 20, 2024 2:45 AM
> To: intel-wired-lan@lists.osuosl.org
> Cc: netdev@vger.kernel.org; Kitszel, Przemyslaw <przemyslaw.kitszel@intel.com>
> Subject: [Intel-wired-lan] [PATCH iwl-net] ice: Add check for lport extraction to LAG init
>
> To fully support initializing the LAG support code, a DDP package that
> extracts the logical port from the metadata is required. If such a
> package is not present, there could be difficulties in supporting some
> bond types.
>
> Add a check into the initialization flow that will bypass the new paths
> if any of the support pieces are missing.
>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Fixes: df006dd4b1dc ("ice: Add initial support framework for LAG")
> Signed-off-by: Dave Ertman <david.m.ertman@intel.com>
> ---
> drivers/net/ethernet/intel/ice/ice_lag.c | 25 ++++++++++++++++++++++--
> drivers/net/ethernet/intel/ice/ice_lag.h | 3 +++
> 2 files changed, 26 insertions(+), 2 deletions(-)
>
Tested-by: Pucha Himasekhar Reddy <himasekharx.reddy.pucha@intel.com> (A Contingent worker at Intel)
prev parent reply other threads:[~2024-02-09 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 21:15 [PATCH iwl-net] ice: Add check for lport extraction to LAG init Dave Ertman
2024-01-22 12:36 ` [Intel-wired-lan] " Marcin Szycik
2024-01-22 19:49 ` Simon Horman
2024-01-30 14:31 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2024-02-09 11:08 ` Pucha, HimasekharX Reddy [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=CYYPR11MB8429B8B327BD807EE4761671BD4B2@CYYPR11MB8429.namprd11.prod.outlook.com \
--to=himasekharx.reddy.pucha@intel.com \
--cc=david.m.ertman@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@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;
as well as URLs for NNTP newsgroup(s).