From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Somnath Kotur <somnath.kotur@broadcom.com>,
Lance Richardson <lance.richardson@broadcom.com>
Cc: dev <dev@dpdk.org>,
Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>,
Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] net/bnxt: set Rx checksum flags in vector mode receive
Date: Tue, 30 Jul 2019 18:23:24 +0100 [thread overview]
Message-ID: <bd81eba3-c7e0-60f4-1ead-e3bc1a43ab4b@intel.com> (raw)
In-Reply-To: <CAOBf=muquHRtS+gURS+PKOFuSj6iM4jDuRHwLS1j8FdY+OxiwQ@mail.gmail.com>
On 7/30/2019 4:45 PM, Somnath Kotur wrote:
> On Tue, Jul 30, 2019 at 2:58 AM Lance Richardson
> <lance.richardson@broadcom.com> wrote:
>>
>> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>>
>> Fixed to return the checksum status of rx packets by setting
>> "ol_flags" correctly in vector mode receive.
>>
>> These changes have been there for non vector mode receive.
>> In vector mode receive also indicate inner and outer checksum
>> errors individually in "ol_flag" to indicate L3 and L4 error.
>>
>> Fixes: bc4a000f2f53 ("net/bnxt: implement SSE vector mode")
>>
>> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>> Reviewed-by: Lance Richardson <lance.richardson@broadcom.com>
>> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
>
> Acked-by: Somnath Kotur <somnath.kotur@broadcom.com>
>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-07-30 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 21:28 Lance Richardson
2019-07-30 15:32 ` Ferruh Yigit
2019-07-30 15:45 ` Somnath Kotur
2019-07-30 15:45 ` Somnath Kotur
2019-07-30 17:23 ` Ferruh Yigit [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=bd81eba3-c7e0-60f4-1ead-e3bc1a43ab4b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=lance.richardson@broadcom.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).