From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Shijith Thotton <sthotton@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [PATCH 1/2] event/cnxk: fix incorrect mask length
Date: Thu, 3 Mar 2022 12:20:24 +0530 [thread overview]
Message-ID: <CALBAE1M5aDxNjwQPZdCWUsDrj8kM7qoTUq=cByd1eqy3y9aMzg@mail.gmail.com> (raw)
In-Reply-To: <20220301225309.8126-1-pbhagavatula@marvell.com>
On Wed, Mar 2, 2022 at 4:23 AM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Fix incorrect mask used when clearing subevent type masking out
> useful data.
>
> Fixes: e239e0d3faf7 ("event/cnxk: add SSO HW device operations")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Series applied to dpdk-next-net-eventdev/for-main. Thanks
> ---
> drivers/event/cnxk/cnxk_eventdev.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/event/cnxk/cnxk_eventdev.h b/drivers/event/cnxk/cnxk_eventdev.h
> index b157fef096..5564746e6d 100644
> --- a/drivers/event/cnxk/cnxk_eventdev.h
> +++ b/drivers/event/cnxk/cnxk_eventdev.h
> @@ -43,7 +43,7 @@
> #define CNXK_TT_FROM_EVENT(x) (((x) >> 38) & SSO_TT_EMPTY)
> #define CNXK_EVENT_TYPE_FROM_TAG(x) (((x) >> 28) & 0xf)
> #define CNXK_SUB_EVENT_FROM_TAG(x) (((x) >> 20) & 0xff)
> -#define CNXK_CLR_SUB_EVENT(x) (~(0xffu << 20) & x)
> +#define CNXK_CLR_SUB_EVENT(x) (~(0xffull << 20) & x)
> #define CNXK_GRP_FROM_TAG(x) (((x) >> 36) & 0x3ff)
> #define CNXK_SWTAG_PEND(x) (BIT_ULL(62) & x)
> #define CNXK_TAG_IS_HEAD(x) (BIT_ULL(35) & x)
> --
> 2.17.1
>
prev parent reply other threads:[~2022-03-03 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 22:53 pbhagavatula
2022-03-01 22:53 ` [PATCH 2/2] event/cnxk: fix incorrect Rx adapter config checks pbhagavatula
2022-03-03 6:50 ` 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='CALBAE1M5aDxNjwQPZdCWUsDrj8kM7qoTUq=cByd1eqy3y9aMzg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=sthotton@marvell.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).