From: Feifei Wang <Feifei.Wang2@arm.com>
To: dpdk stable <stable@dpdk.org>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: Paolo Valerio <pvalerio@redhat.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>, nd <nd@arm.com>
Subject: [dpdk-stable] 回复: please help backporting some patches to stable release 19.11.7
Date: Fri, 19 Feb 2021 06:23:03 +0000 [thread overview]
Message-ID: <DBBPR08MB44117DA338A6FB36DDB369B4C8849@DBBPR08MB4411.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20210215133002.1856070-1-christian.ehrhardt@canonical.com>
Hi, Christian
The patch 'b9c366e029' depends on the following two patch series:
1. Enable Checksum Offloading for NEON vector
a). net/ixgbe: add new flag of stripped VLAN for NEON vector
b). net/ixgbe: support bad checksum flag for NEON vector
c). net/ixgbe: support good checksum flag for NEON vector
d). net/ixgbe: enable IXGBE NEON vector when need to checksum
These patches weren't added fix bug tag when they are merged, and I just have sent them to stable@dpdk.org.
2. net/ixgbe: fix UDP zero checksum on x86: 9a40edb599d76f7f9d116bb2f91b23c082b5f154
This patch is not merged to 19.11 version.
I think if above two series are merged to 19.11, the conflicts and errors can be fixed.
Best Regards
Feifei
> -----邮件原件-----
> 发件人: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> 发送时间: 2021年2月15日 21:30
> 抄送: Feifei Wang <Feifei.Wang2@arm.com>; Paolo Valerio
> <pvalerio@redhat.com>; Ruifeng Wang <Ruifeng.Wang@arm.com>
> 主题: please help backporting some patches to stable release 19.11.7
>
> Hi commit authors (and maintainers),
>
> I didn't apply following commits from DPDK main to 19.11 stable branch, as
> conflicts or build errors occur.
>
> Can authors check your patches in the following list and either:
> - Backport your patches to the 19.11 branch, or
> - Indicate that the patch should not be backported
>
> Please do either of the above by 02/22/21.
>
> You can find the a temporary work-in-progress branch of the coming 19.11.7
> release at:
> https://github.com/cpaelzer/dpdk-stable-queue
> It is recommended to backport on top of that to minimize further conflicts or
> misunderstandings.
>
> Some notes on stable backports:
>
> A backport should contain a reference to the DPDK main branch commit in it's
> commit message in the following fashion:
> [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]
>
> For example:
> https://git.dpdk.org/dpdk-
> stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb
>
> When sending the backported patch, please indicate the target branch in the
> subject line, as we have multiple branches, for example:
> [PATCH 19.11] foo/bar: fix baz
>
> With git format-patch, this can be achieved by appending the parameter:
> --subject-prefix='PATCH 19.11'
>
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>
> FYI, branch 19.11 is located at tree:
> https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
> ---
> b9c366e029 Feifei Wang net/ixgbe: fix UDP zero checksum on Arm
next parent reply other threads:[~2021-02-19 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210215133002.1856070-1-christian.ehrhardt@canonical.com>
2021-02-19 6:23 ` Feifei Wang [this message]
[not found] <20210204115554.2506672-1-christian.ehrhardt@canonical.com>
2021-02-04 14:43 ` [dpdk-stable] " Richardson, Bruce
2021-02-04 16:59 ` Maxime Coquelin
2021-02-04 20:16 ` Dmitry Kozlyuk
2021-02-08 16:39 ` Lance Richardson
2021-02-12 8:11 ` Christian Ehrhardt
2021-02-12 9:16 ` Richardson, Bruce
2021-02-12 14:38 ` Slava Ovsiienko
2021-02-19 8:18 ` Somnath Kotur
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=DBBPR08MB44117DA338A6FB36DDB369B4C8849@DBBPR08MB4411.eurprd08.prod.outlook.com \
--to=feifei.wang2@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=christian.ehrhardt@canonical.com \
--cc=nd@arm.com \
--cc=pvalerio@redhat.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).