patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Guinan Sun <guinanx.sun@intel.com>, dev@dpdk.org
Cc: Zhao1 Wei <wei.zhao1@intel.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/ixgbe: fix MACsec private API
Date: Fri, 22 May 2020 10:17:06 +0100	[thread overview]
Message-ID: <a5169bbc-6d8e-7e91-6c34-2211e6aa5346@redhat.com> (raw)
In-Reply-To: <20200522055955.30712-1-guinanx.sun@intel.com>

On 22/05/2020 06:59, Guinan Sun wrote:
> The driver type need to be checked in private API.
> The patch fixes the issue.
> 
> Fixes: 50556c88104c ("net/ixgbe: fix MACsec setting")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Guinan Sun <guinanx.sun@intel.com>
> ---
>  drivers/net/ixgbe/rte_pmd_ixgbe.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/net/ixgbe/rte_pmd_ixgbe.c b/drivers/net/ixgbe/rte_pmd_ixgbe.c
> index 8bcaded6e..9bff557f9 100644
> --- a/drivers/net/ixgbe/rte_pmd_ixgbe.c
> +++ b/drivers/net/ixgbe/rte_pmd_ixgbe.c
> @@ -522,6 +522,9 @@ rte_pmd_ixgbe_macsec_enable(uint16_t port, uint8_t en, uint8_t rp)
>  
>  	dev = &rte_eth_devices[port];
>  
> +	if (!is_ixgbe_supported(dev))
> +		return -ENOTSUP;
> +
>  	macsec_setting.offload_en = 1;
>  	macsec_setting.encrypt_en = en;
>  	macsec_setting.replayprotect_en = rp;
> @@ -542,6 +545,9 @@ rte_pmd_ixgbe_macsec_disable(uint16_t port)
>  
>  	dev = &rte_eth_devices[port];
>  
> +	if (!is_ixgbe_supported(dev))
> +		return -ENOTSUP;
> +
>  	ixgbe_dev_macsec_setting_reset(dev);
>  
>  	ixgbe_dev_macsec_register_disable(dev);
> 

Acked-by: Kevin Traynor <ktraynor@redhat.com>


  parent reply	other threads:[~2020-05-22  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  5:59 [dpdk-stable] " Guinan Sun
2020-05-22  9:11 ` Ye Xiaolong
2020-05-22  9:17 ` Kevin Traynor [this message]
2020-05-22 15:13 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit

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=a5169bbc-6d8e-7e91-6c34-2211e6aa5346@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=dev@dpdk.org \
    --cc=guinanx.sun@intel.com \
    --cc=stable@dpdk.org \
    --cc=wei.zhao1@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).