From: Jerin Jacob <jerinjacobk@gmail.com>
To: Tomasz Duszynski <tduszynski@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] common/cnxk: fix a few typos
Date: Wed, 3 Nov 2021 20:42:15 +0530 [thread overview]
Message-ID: <CALBAE1OuxWMrZWA3Lb8dwSg1dRGUzZn2uB199f1twRgV93ArOw@mail.gmail.com> (raw)
In-Reply-To: <20211102184713.3012645-1-tduszynski@marvell.com>
On Wed, Nov 3, 2021 at 12:18 AM Tomasz Duszynski <tduszynski@marvell.com> wrote:
>
> Fix typos here and there.
>
> Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
> Reviewed-by: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Changed to
common/cnxk: fix a few typos
Fix a few typos.
Fixes: fa8f86a14e2e ("common/cnxk: add build infrastructre and HW
definition")
Fixes: f6d567b03d28 ("common/cnxk: support NIX IRQ")
Fixes: 5e076b609f2a ("common/cnxk: add SE set key for crypto")
Cc: stable@dpdk.org
Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/for-next-net. Thanks
> ---
> drivers/common/cnxk/roc_api.h | 2 +-
> drivers/common/cnxk/roc_nix_irq.c | 2 +-
> drivers/common/cnxk/roc_se.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/common/cnxk/roc_api.h b/drivers/common/cnxk/roc_api.h
> index b8f3667c6c..63c7df7b6c 100644
> --- a/drivers/common/cnxk/roc_api.h
> +++ b/drivers/common/cnxk/roc_api.h
> @@ -12,7 +12,7 @@
> /* Bits manipulation */
> #include "roc_bits.h"
>
> -/* Bitfields manipulation */
> +/* Bit fields manipulation */
> #include "roc_bitfield.h"
>
> /* ROC Constants */
> diff --git a/drivers/common/cnxk/roc_nix_irq.c b/drivers/common/cnxk/roc_nix_irq.c
> index e9aa620abd..a5cd9d4b02 100644
> --- a/drivers/common/cnxk/roc_nix_irq.c
> +++ b/drivers/common/cnxk/roc_nix_irq.c
> @@ -421,7 +421,7 @@ roc_nix_register_cq_irqs(struct roc_nix *roc_nix)
> rc);
> return rc;
> }
> - /* VFIO vector zero is resereved for misc interrupt so
> + /* VFIO vector zero is reserved for misc interrupt so
> * doing required adjustment. (b13bfab4cd)
> */
> if (plt_intr_vec_list_index_set(handle, q,
> diff --git a/drivers/common/cnxk/roc_se.c b/drivers/common/cnxk/roc_se.c
> index 4edbc8e547..6a28609b7c 100644
> --- a/drivers/common/cnxk/roc_se.c
> +++ b/drivers/common/cnxk/roc_se.c
> @@ -357,7 +357,7 @@ roc_se_ciph_key_set(struct roc_se_ctx *se_ctx, roc_se_cipher_type type,
> if (se_ctx->fc_type == ROC_SE_FC_GEN) {
> /*
> * We need to always say IV is from DPTR as user can
> - * sometimes iverride IV per operation.
> + * sometimes override IV per operation.
> */
> fctx->enc.iv_source = ROC_SE_FROM_DPTR;
>
> --
> 2.25.1
>
prev parent reply other threads:[~2021-11-03 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 18:47 Tomasz Duszynski
2021-11-03 15:12 ` 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=CALBAE1OuxWMrZWA3Lb8dwSg1dRGUzZn2uB199f1twRgV93ArOw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=tduszynski@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).