From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiaoyun wang <cloud.wangxiaoyun@huawei.com>, dev@dpdk.org
Cc: bluca@debian.org, stable@dpdk.org, luoxingyu@huawei.com,
luoxianjun@huawei.com, yin.yinshi@huawei.com,
zhouguoyang@huawei.com
Subject: Re: [dpdk-stable] [PATCH v1 0/2] fix some csum errors
Date: Mon, 2 Nov 2020 17:47:25 +0000 [thread overview]
Message-ID: <1f6945fa-0a1a-244a-d1a2-e2724be209be@intel.com> (raw)
In-Reply-To: <cover.1604115055.git.cloud.wangxiaoyun@huawei.com>
On 10/31/2020 3:38 AM, Xiaoyun wang wrote:
> This patch fixes outer_l3_len parse error when
> PKT_TX_OUTER_IP_CKSUM is not set, which does not affect
> checksum function, just be consistent with mbuf meta
> information description, and fixes SCTP checksum
> errors because driver doesn't pass payload offset info
> to hardware, which may cause SCTP checksum error.
>
> --
>
> v1:
> - fix outer_l3_len parse error
> - fix SCTP checksum error
>
> Xiaoyun wang (2):
> net/hinic: fix outer_l3_len parse error
> net/hinic: fix SCTP checksum error
>
Series applied to dpdk-next-net/main, thanks.
Also can you please review a long waiting [1] hinic patch:
https://patches.dpdk.org/patch/83421/
[1]
Current patch doesn't have version information but it is continuation of the
patch from early August:
https://patches.dpdk.org/project/dpdk/list/?series=&submitter=1866&state=*&q=net%2Fhinic&archive=&delegate=
prev parent reply other threads:[~2020-11-02 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 3:38 Xiaoyun wang
2020-10-31 3:38 ` [dpdk-stable] [PATCH v1 1/2] net/hinic: fix outer_l3_len parse error Xiaoyun wang
2020-11-02 17:08 ` Ferruh Yigit
2020-11-02 17:26 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2020-11-04 2:19 ` [dpdk-stable] " Wangxiaoyun (Cloud)
2020-11-04 11:05 ` Ferruh Yigit
2020-10-31 3:38 ` [dpdk-stable] [PATCH v1 2/2] net/hinic: fix SCTP checksum error Xiaoyun wang
2020-11-02 17:47 ` 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=1f6945fa-0a1a-244a-d1a2-e2724be209be@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bluca@debian.org \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=dev@dpdk.org \
--cc=luoxianjun@huawei.com \
--cc=luoxingyu@huawei.com \
--cc=stable@dpdk.org \
--cc=yin.yinshi@huawei.com \
--cc=zhouguoyang@huawei.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).