From: Simon Horman <simon.horman@corigine.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: intel-wired-lan@lists.osuosl.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>,
Sudheer Mogilappagari <sudheer.mogilappagari@intel.com>,
aleksander.lobakin@intel.com, netdev@vger.kernel.org
Subject: Re: [PATCH iwl-next] ice: clean up __ice_aq_get_set_rss_lut()
Date: Tue, 6 Jun 2023 17:38:19 +0200 [thread overview]
Message-ID: <ZH9S6wPIg9os8HYa@corigine.com> (raw)
In-Reply-To: <20230606111149.33890-1-przemyslaw.kitszel@intel.com>
On Tue, Jun 06, 2023 at 01:11:49PM +0200, Przemek Kitszel wrote:
...
> diff --git a/drivers/net/ethernet/intel/ice/ice_common.c b/drivers/net/ethernet/intel/ice/ice_common.c
> index 6acb40f3c202..af4c8ddcafb0 100644
> --- a/drivers/net/ethernet/intel/ice/ice_common.c
> +++ b/drivers/net/ethernet/intel/ice/ice_common.c
> @@ -3869,6 +3869,30 @@ ice_aq_sff_eeprom(struct ice_hw *hw, u16 lport, u8 bus_addr,
> return status;
> }
>
> +static enum ice_lut_size ice_lut_type_to_size(enum ice_lut_type type)
> +{
> + switch (type) {
> + case ICE_LUT_VSI:
> + return ICE_LUT_VSI_SIZE;
> + case ICE_LUT_GLOBAL:
> + return ICE_LUT_GLOBAL_SIZE;
> + case ICE_LUT_PF:
> + return ICE_LUT_PF_SIZE;
> + }
Hi Przemek,
I see where you are going here, but gcc-12 W=1 wants a return here.
> +}
> +
> +static enum ice_aqc_lut_flags ice_lut_size_to_flag(enum ice_lut_size size)
> +{
> + switch (size) {
> + case ICE_LUT_VSI_SIZE:
> + return ICE_AQC_LUT_SIZE_SMALL;
> + case ICE_LUT_GLOBAL_SIZE:
> + return ICE_AQC_LUT_SIZE_512;
> + case ICE_LUT_PF_SIZE:
> + return ICE_AQC_LUT_SIZE_2K;
> + }
And here.
> +}
> +
> /**
> * __ice_aq_get_set_rss_lut
> * @hw: pointer to the hardware structure
--
pw-bot: cr
next prev parent reply other threads:[~2023-06-06 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 11:11 [PATCH iwl-next] ice: clean up __ice_aq_get_set_rss_lut() Przemek Kitszel
2023-06-06 13:31 ` Alexander Lobakin
2023-06-07 12:56 ` Przemek Kitszel
2023-06-06 15:38 ` Simon Horman [this message]
2023-06-06 15:42 ` Alexander Lobakin
2023-06-06 16:39 ` Simon Horman
2023-06-06 21:14 ` Przemek Kitszel
2023-06-07 7:34 ` Simon Horman
2023-06-07 16:42 ` Jakub Kicinski
2023-06-07 20:38 ` Simon Horman
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=ZH9S6wPIg9os8HYa@corigine.com \
--to=simon.horman@corigine.com \
--cc=aleksander.lobakin@intel.com \
--cc=anirudh.venkataramanan@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=sudheer.mogilappagari@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).