DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>,
	dpdk-dev <dev@dpdk.org>,
	 Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	nd <nd@arm.com>
Subject: Re: [PATCH 0/3] BNXT changes
Date: Mon, 9 May 2022 22:17:29 -0700	[thread overview]
Message-ID: <CACZ4nhu8Rk3-d72cYn7q0e4RTyqWfViuRP2Ts0XHNjrUVZsiNg@mail.gmail.com> (raw)
In-Reply-To: <CACZ4nhv7O+1WbYQ+Y=Mtb_CQFiqMkP=M5_VjOQBvaEBqZcDgvQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

On Wed, Apr 13, 2022 at 3:12 PM Ajit Khaparde
<ajit.khaparde@broadcom.com> wrote:
>
> On Wed, Apr 13, 2022 at 3:32 AM Ruifeng Wang <ruifeng.wang@arm.com> wrote:
> >
> > This patch set includes changes proposed for BNXT PMD.
> > Found these in code review.
> >
> > Ruifeng Wang (3):
> >   net/bnxt: defer completion index update
> >   net/bnxt: remove redundant ifdefs
> >   net/bnxt: fix risk in Rx descriptor read in NEON path
> Thanks Ruifeng.
> Let me review the patchset and get back.

Patches applied to dpdk-next-net-brcm. Thanks
>
> >
> >  drivers/net/bnxt/bnxt_rxr.c           |  2 +-
> >  drivers/net/bnxt/bnxt_rxtx_vec_neon.c | 21 +++++++++++++++------
> >  2 files changed, 16 insertions(+), 7 deletions(-)
> >
> > --
> > 2.25.1
> >

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]

      reply	other threads:[~2022-05-10  5:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 10:31 Ruifeng Wang
2022-04-13 10:31 ` [PATCH 1/3] net/bnxt: defer completion index update Ruifeng Wang
2022-04-13 10:31 ` [PATCH 2/3] net/bnxt: remove redundant ifdefs Ruifeng Wang
2022-04-13 10:31 ` [PATCH 3/3] net/bnxt: fix risk in Rx descriptor read in NEON path Ruifeng Wang
2022-04-13 22:12 ` [PATCH 0/3] BNXT changes Ajit Khaparde
2022-05-10  5:17   ` Ajit Khaparde [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=CACZ4nhu8Rk3-d72cYn7q0e4RTyqWfViuRP2Ts0XHNjrUVZsiNg@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=nd@arm.com \
    --cc=ruifeng.wang@arm.com \
    --cc=somnath.kotur@broadcom.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).