From: Lance Richardson <lance.richardson@broadcom.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>
Cc: dev@dpdk.org, dpdk stable <stable@dpdk.org>,
Andy Gospodarek <gospo@broadcom.com>
Subject: Re: [dpdk-stable] [PATCH] net/bnxt: fix Rx descriptor status
Date: Tue, 2 Mar 2021 11:07:07 -0500 [thread overview]
Message-ID: <CADyeNEC3DCZA6iVRJ9WMJqh+iDrFf85pTNC8zxGiBiSOvh2TJA@mail.gmail.com> (raw)
In-Reply-To: <20210302142927.536372-1-lance.richardson@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Tue, Mar 2, 2021 at 9:29 AM Lance Richardson
<lance.richardson@broadcom.com> wrote:
>
> Fix a number of issues in the bnxt receive descriptor status
> function, including:
> - Provide status of receive descriptor instead of completion
> descriptor.
> - Remove invalid comparison of raw ring index with masked ring
> index.
> - Correct misinterpretation of offset parameter as ring index.
> - Correct misuse of completion ring index for mbuf ring (the
> two rings have different sizes).
>
> Fixes: 0fe613bb87b2 ("net/bnxt: support Rx descriptor status")
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
> Cc: stable@dpdk.org
> Reviewed-by: Andy Gospodarek <gospo@broadcom.com>
> Reviewed-by: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>
> ---
This patch has a dependency on:
http://patchwork.dpdk.org/project/dpdk/list/?series=15289&archive=both&state=*
next prev parent reply other threads:[~2021-03-02 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 14:29 Lance Richardson
2021-03-02 16:07 ` Lance Richardson [this message]
2021-03-11 18:28 ` [dpdk-stable] [PATCH v2] " Ajit Khaparde
2021-03-11 20:04 ` [dpdk-stable] [PATCH v3] " Ajit Khaparde
2021-03-11 23:54 ` Ajit Khaparde
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=CADyeNEC3DCZA6iVRJ9WMJqh+iDrFf85pTNC8zxGiBiSOvh2TJA@mail.gmail.com \
--to=lance.richardson@broadcom.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=gospo@broadcom.com \
--cc=somnath.kotur@broadcom.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).