Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Neftin, Sasha <sasha.neftin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 2/2] igc: Fix IGC_MAX_RXNFC_RULES
Date: Wed, 13 May 2020 09:59:13 +0300	[thread overview]
Message-ID: <3cb071e1-28d4-c885-bc64-d5ab03cf9578@intel.com> (raw)
In-Reply-To: <20200512173553.39460-2-andre.guedes@intel.com>

On 5/12/2020 20:35, Andre Guedes wrote:
> IGC supports a total of 32 rules. 16 MAC address based, 8 VLAN priority
> based, and 8 ethertype based. This patch fixes IGC_MAX_RXNFC_RULES
> accordingly.
> 
> Signed-off-by: Andre Guedes <andre.guedes@intel.com>
> ---
>   drivers/net/ethernet/intel/igc/igc.h | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/intel/igc/igc.h b/drivers/net/ethernet/intel/igc/igc.h
> index 14f9edaaaf83..5dbc5a156626 100644
> --- a/drivers/net/ethernet/intel/igc/igc.h
> +++ b/drivers/net/ethernet/intel/igc/igc.h
> @@ -457,7 +457,10 @@ struct igc_nfc_rule {
>   	u16 action;
>   };
>   
> -#define IGC_MAX_RXNFC_RULES		16
> +/* IGC supports a total of 32 NFC rules: 16 MAC address based,, 8 VLAN priority
> + * based, and 8 ethertype based.
> + */
> +#define IGC_MAX_RXNFC_RULES		32
>   
>   /* igc_desc_unused - calculate if we have unused descriptors */
>   static inline u16 igc_desc_unused(const struct igc_ring *ring)
> 
Acked-by: Sasha Neftin <sasha.neftin@intel.com>

      reply	other threads:[~2020-05-13  6:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 17:35 [Intel-wired-lan] [PATCH 1/2] igc: Reject NFC rules with multiple matches Andre Guedes
2020-05-12 17:35 ` [Intel-wired-lan] [PATCH 2/2] igc: Fix IGC_MAX_RXNFC_RULES Andre Guedes
2020-05-13  6:59   ` Neftin, Sasha [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=3cb071e1-28d4-c885-bc64-d5ab03cf9578@intel.com \
    --to=sasha.neftin@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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