intel-wired-lan.lists.osuosl.org archive mirror
 help / color / mirror / Atom feed
From: "Pucha, HimasekharX Reddy" <himasekharx.reddy.pucha@intel.com>
To: "Polchlopek, Mateusz" <mateusz.polchlopek@intel.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Polchlopek, Mateusz" <mateusz.polchlopek@intel.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
	"Tipireddy, Vaishnavi" <vaishnavi.tipireddy@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1] ice: refactor struct ice_vsi_cfg_params to be inside of struct ice_vsi
Date: Thu, 25 Apr 2024 12:50:40 +0000	[thread overview]
Message-ID: <CYYPR11MB8429EBF18D0D54B405DE08FEBD172@CYYPR11MB8429.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240419091104.13495-1-mateusz.polchlopek@intel.com>

> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of Mateusz Polchlopek
> Sent: Friday, April 19, 2024 2:41 PM
> To: intel-wired-lan@lists.osuosl.org
> Cc: netdev@vger.kernel.org; Tipireddy, Vaishnavi <vaishnavi.tipireddy@intel.com>; Nguyen, Anthony L <anthony.l.nguyen@intel.com>; Kitszel, Przemyslaw <przemyslaw.kitszel@intel.com>; Polchlopek, Mateusz <mateusz.polchlopek@intel.com>
> Subject: [Intel-wired-lan] [PATCH iwl-next v1] ice: refactor struct ice_vsi_cfg_params to be inside of struct ice_vsi
>
> Refactor struct ice_vsi_cfg_params to be embedded into struct ice_vsi.
> Prior to that the members of the struct were scattered around ice_vsi, and were copy-pasted for purposes of reinit.
> Now we have struct handy, and it is easier to have something sticky in the flags field.
>
> Suggested-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Reviewed-by: Vaishnavi Tipireddy <vaishnavi.tipireddy@intel.com>
> Signed-off-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
> ---
>  .../net/ethernet/intel/ice/devlink/devlink.c  |  6 +--
>  drivers/net/ethernet/intel/ice/ice.h          | 14 ++++---
>  drivers/net/ethernet/intel/ice/ice_lib.c      | 33 ++++++----------
>  drivers/net/ethernet/intel/ice/ice_lib.h      | 39 +------------------
>  drivers/net/ethernet/intel/ice/ice_main.c     |  8 ++--
>  drivers/net/ethernet/intel/ice/ice_sriov.c    |  2 +-
>  drivers/net/ethernet/intel/ice/ice_vf_lib.c   |  8 ++--
>  7 files changed, 30 insertions(+), 80 deletions(-)
>

Tested-by: Pucha Himasekhar Reddy <himasekharx.reddy.pucha@intel.com> (A Contingent worker at Intel)


      reply	other threads:[~2024-04-25 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  9:11 [Intel-wired-lan] [PATCH iwl-next v1] ice: refactor struct ice_vsi_cfg_params to be inside of struct ice_vsi Mateusz Polchlopek
2024-04-25 12:50 ` 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=CYYPR11MB8429EBF18D0D54B405DE08FEBD172@CYYPR11MB8429.namprd11.prod.outlook.com \
    --to=himasekharx.reddy.pucha@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=mateusz.polchlopek@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=vaishnavi.tipireddy@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 read-only IMAP folder(s) and NNTP newsgroup(s).