From: Akhil Goyal <gakhil@marvell.com>
To: Srujana Challa <schalla@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Koteswara Rao Kottidi <skoteshwar@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] common/cnxk: fix attaching NPA LF to CPT VF
Date: Wed, 8 Sep 2021 12:06:28 +0000 [thread overview]
Message-ID: <CO6PR18MB4484C4CBBD4ADA0973D846D6D8D49@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210818115635.3526239-1-schalla@marvell.com>
> ATTACH_RESOURCES mailbox for CPT LFs is being called without
> setting modify bit. Because of this previously attached NPA LF
> to the CPT VF is getting removed, when only CPT VF is whitelisted.
> This patch fixes the same.
>
> Fixes: c045d2e5cbbc ("common/cnxk: add CPT configuration")
>
> v2:
> - Fixed checkpatch warning.
Changelog should be mentioned after ---
Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
>
> Signed-off-by: Srujana Challa <schalla@marvell.com>
> ---
> drivers/common/cnxk/roc_cpt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/common/cnxk/roc_cpt.c
> b/drivers/common/cnxk/roc_cpt.c
> index 2ffd271566..60a68876b0 100644
> --- a/drivers/common/cnxk/roc_cpt.c
> +++ b/drivers/common/cnxk/roc_cpt.c
> @@ -478,7 +478,7 @@ roc_cpt_dev_configure(struct roc_cpt *roc_cpt, int
> nb_lf)
> int rc, i;
>
> /* Request LF resources */
> - rc = cpt_lfs_attach(&cpt->dev, blkaddr, false, nb_lf);
> + rc = cpt_lfs_attach(&cpt->dev, blkaddr, true, nb_lf);
> if (rc)
> return rc;
>
> --
> 2.25.1
prev parent reply other threads:[~2021-09-08 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 11:56 Srujana Challa
2021-09-08 12:06 ` Akhil Goyal [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=CO6PR18MB4484C4CBBD4ADA0973D846D6D8D49@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=schalla@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=thomas@monjalon.net \
/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).