[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MW5PR11MB5811B6646C1096BE62B625CADD51A@MW5PR11MB5811.namprd11.prod.outlook.com>
Date: Fri, 9 Jun 2023 16:34:50 +0000
From: "Ertman, David M" <david.m.ertman@...el.com>
To: Daniel Machon <daniel.machon@...rochip.com>
CC: "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH iwl-next v3 04/10] ice: implement lag netdev event handler
> -----Original Message-----
> From: Daniel Machon <daniel.machon@...rochip.com>
> Sent: Friday, June 9, 2023 3:01 AM
> To: Ertman, David M <david.m.ertman@...el.com>
> Cc: intel-wired-lan@...ts.osuosl.org; netdev@...r.kernel.org
> Subject: Re: [PATCH iwl-next v3 04/10] ice: implement lag netdev event
> handler
>
> Hi Dave,
>
> This patch fails to build, as ice_lag_move_new_vf_nodes() is used in
> ice_vc_cfg_qs_msg(), but first defined in the next patch.
Thanks for catching that - I moved some code around and neglected to do a patch by
patch build test. I have some refactoring to do for another feedback and will run the
test before I send out v4.
Thanks for the review!
DaveE
>
> > The event handler for LAG will create a work item to place on the ordered
> > workqueue to be processed.
> >
> > Add in defines for training packets and new recipes to be used by the
> > switching block of the HW for LAG packet steering.
> >
> > Update the ice_lag struct to reflect the new processing methodology.
> >
> > Signed-off-by: Dave Ertman <david.m.ertman@...el.com>
> > ---
> > drivers/net/ethernet/intel/ice/ice_lag.c | 125 ++++++++++++++++--
> > drivers/net/ethernet/intel/ice/ice_lag.h | 31 ++++-
> > drivers/net/ethernet/intel/ice/ice_virtchnl.c | 2 +
> > 3 files changed, 144 insertions(+), 14 deletions(-)
> >
Powered by blists - more mailing lists