netdev - RE: [Intel-wired-lan] [iwl-next v3 7/8] iavf: use libie_aq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <IA3PR11MB8986139F4B98A2A4D2D40017E55EA@IA3PR11MB8986.namprd11.prod.outlook.com>
Date: Thu, 24 Jul 2025 08:20:05 +0000
From: "Loktionov, Aleksandr" <aleksandr.loktionov@...el.com>
To: "Romanowski, Rafal" <rafal.romanowski@...el.com>, Michal Swiatkowski
	<michal.swiatkowski@...ux.intel.com>, "intel-wired-lan@...ts.osuosl.org"
	<intel-wired-lan@...ts.osuosl.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "Lobakin, Aleksander"
	<aleksander.lobakin@...el.com>, "Kitszel, Przemyslaw"
	<przemyslaw.kitszel@...el.com>, "Kwapulinski, Piotr"
	<piotr.kwapulinski@...el.com>, "Jagielski, Jedrzej"
	<jedrzej.jagielski@...el.com>, "Zaremba, Larysa" <larysa.zaremba@...el.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>
Subject: RE: [Intel-wired-lan] [iwl-next v3 7/8] iavf: use libie_aq_str



> -----Original Message-----
> From: Romanowski, Rafal <rafal.romanowski@...el.com>
> Sent: Thursday, July 24, 2025 9:12 AM
> To: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>; intel-
> wired-lan@...ts.osuosl.org
> Cc: netdev@...r.kernel.org; Lobakin, Aleksander
> <aleksander.lobakin@...el.com>; Kitszel, Przemyslaw
> <przemyslaw.kitszel@...el.com>; Kwapulinski, Piotr
> <piotr.kwapulinski@...el.com>; Loktionov, Aleksandr
> <aleksandr.loktionov@...el.com>; Jagielski, Jedrzej
> <jedrzej.jagielski@...el.com>; Zaremba, Larysa
> <larysa.zaremba@...el.com>; Nguyen, Anthony L
> <anthony.l.nguyen@...el.com>
> Subject: RE: [Intel-wired-lan] [iwl-next v3 7/8] iavf: use
> libie_aq_str
> 
> > -----Original Message-----
> > From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf
> > Of Michal Swiatkowski
> > Sent: Friday, April 25, 2025 8:08 AM
> > To: intel-wired-lan@...ts.osuosl.org
> > Cc: netdev@...r.kernel.org; Lobakin, Aleksander
> > <aleksander.lobakin@...el.com>; Kitszel, Przemyslaw
> > <przemyslaw.kitszel@...el.com>; Kwapulinski, Piotr
> > <piotr.kwapulinski@...el.com>; Loktionov, Aleksandr
> > <aleksandr.loktionov@...el.com>; Jagielski, Jedrzej
> > <jedrzej.jagielski@...el.com>; Zaremba, Larysa
> > <larysa.zaremba@...el.com>; Nguyen, Anthony L
> > <anthony.l.nguyen@...el.com>
> > Subject: [Intel-wired-lan] [iwl-next v3 7/8] iavf: use libie_aq_str
> >
> > There is no need to store the err string in hw->err_str. Simplify it
> > and use common helper. hw->err_str is still used for other purpouse.
> >
> > It should be marked that previously for unknown error the numeric
> > value was passed as a string. Now the "LIBIE_AQ_RC_UNKNOWN" is used
> for such cases.
> >
> > Add libie_aminq module in iavf Kconfig.
> >
> > Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@...el.com>
> > Reviewed-by: Larysa Zaremba <larysa.zaremba@...el.com>
> > Signed-off-by: Michal Swiatkowski
> <michal.swiatkowski@...ux.intel.com>
> > ---
> >  drivers/net/ethernet/intel/Kconfig            |  1 +
> >  .../net/ethernet/intel/iavf/iavf_prototype.h  |  1 -
> > drivers/net/ethernet/intel/iavf/iavf_common.c | 52 -----------------
> --
> >  drivers/net/ethernet/intel/iavf/iavf_main.c   |  5 +-
> >  .../net/ethernet/intel/iavf/iavf_virtchnl.c   |  2 +-
> >  5 files changed, 5 insertions(+), 56 deletions(-)
> >
> > diff --git a/drivers/net/ethernet/intel/Kconfig
> > b/drivers/net/ethernet/intel/Kconfig
> > index d5de9bc8b1b6..29c03a9ce145 100644
> > --- a/drivers/net/ethernet/intel/Kconfig
> > +++ b/drivers/net/ethernet/intel/Kconfig
> > @@ -260,6 +260,7 @@ config I40E_DCB
> 
> 
> Tested-by: Rafal Romanowski <rafal.romanowski@...el.com>
> 
Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@...el.com>