DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Harman Kalra <hkalra@marvell.com>, Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
	 Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/octeontx2: fix VF configuration fail
Date: Mon, 13 Jan 2020 12:56:14 +0530	[thread overview]
Message-ID: <CALBAE1OWMf4vtOcNfZfeYE+4FNUEaHThikf_Ji1rekVvKHH6zg@mail.gmail.com> (raw)
In-Reply-To: <1575297605-26773-1-git-send-email-hkalra@marvell.com>

On Mon, Dec 2, 2019 at 8:11 PM Harman Kalra <hkalra@marvell.com> wrote:
>
> Returning -ENOTSUP only in case loopback mode is enabled and
> device is VF or SDP.
>
> Fixes: c2c0aa75cd01 ("net/octeontx2: fix loopback config return for VF")
> Cc: stable@dpdk.org
>
> Signed-off-by: Harman Kalra <hkalra@marvell.com>
> ---

Acked-by: Jerin Jacob <jerinj@marvell.com>

Applied to dpdk-next-net-mrvl/master. Thanks

>  drivers/net/octeontx2/otx2_ethdev.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/octeontx2/otx2_ethdev.c b/drivers/net/octeontx2/otx2_ethdev.c
> index ed329273d..43c6107a8 100644
> --- a/drivers/net/octeontx2/otx2_ethdev.c
> +++ b/drivers/net/octeontx2/otx2_ethdev.c
> @@ -204,7 +204,7 @@ cgx_intlbk_enable(struct otx2_eth_dev *dev, bool en)
>  {
>         struct otx2_mbox *mbox = dev->mbox;
>
> -       if (otx2_dev_is_vf_or_sdp(dev))
> +       if (en && otx2_dev_is_vf_or_sdp(dev))
>                 return -ENOTSUP;
>
>         if (en)
> --
> 2.18.0
>

      reply	other threads:[~2020-01-13  7:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 14:41 Harman Kalra
2020-01-13  7:26 ` Jerin Jacob [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=CALBAE1OWMf4vtOcNfZfeYE+4FNUEaHThikf_Ji1rekVvKHH6zg@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).