From: Kevin Traynor <ktraynor@redhat.com>
To: oulijun <oulijun@huawei.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 18.11.11
Date: Wed, 2 Dec 2020 10:47:10 +0000 [thread overview]
Message-ID: <5d2fbe70-63fd-a965-c640-88f3eb936791@redhat.com> (raw)
In-Reply-To: <71160187-bfa8-f903-33fc-c1e1cb1366bb@huawei.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gbk, Size: 1617 bytes --]
On 01/12/2020 01:53, oulijun wrote:
>
>
> 在 2020/11/28 4:16, Kevin Traynor 写道:
>> Hi commit authors (and maintainers),
>>
>> I didn't apply following commits from DPDK master to 18.11
>> LTS branch, as conflicts or build errors occur. Note, it may be
>> dependent on another patch below that has not been applied.
>>
>> As it is the last 18.11 release and there will not be an opportunity to
>> fix any regressions, I would like to only take backports from the
>> below list at this stage *if* they are deemed important for the 18.11 branch.
>>
>> Can authors check your patches in the following list and either:
>> - Backport your important patches to the 18.11 branch, or
>> - Indicate patch should be dropped from missed list and not backported, or
>> - Take no action => patch will remain on missed list and not be backported
>>
>> Please do the above by 12/02/20.
>>
<snip>
>> 150c9ac2d Wei Hu (Xavier) app/testpmd: update Rx offload after setting MTU
> This patch(150c9ac2d) is not apply for 18.11. Because the 18.11 is not
> get the Rx offload by rte_eth_dev_info_get().
>> 2e02a2aff Wei Hu (Xavier) ethdev: fix VLAN offloads set if no driver callback
> This patch(2e02a2aff) is not apply for 18.11. Because the 18.11 is not
> exist this bug after analysis
ok, thanks for confirming.
>> c52ff3668 Wei Zhao net/i40e: enable QinQ stripping
>> be4ef2e0d Wei Zhao net/i40e: fix flow director enabling
>> dcfbc594f Wei Zhao net/iavf: fix queue interrupt for ice
>> c21e5facf Xueming Li net/mlx5: use bond index for netdev operations
>>
>> .
>>
>
next prev parent reply other threads:[~2020-12-02 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 20:16 Kevin Traynor
2020-12-01 1:53 ` oulijun
2020-12-02 10:47 ` Kevin Traynor [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-24 16:13 Kevin Traynor
2020-11-24 16:30 ` Gregory Etelson
2020-11-24 16:40 ` Kevin Traynor
2020-11-25 2:44 ` Ruifeng Wang
2020-11-25 8:23 ` Thomas Monjalon
2020-11-25 9:19 ` Ruifeng Wang
2020-11-27 10:33 ` Kevin Traynor
2020-11-27 15:10 ` Wang, Haiyue
2020-11-27 15:32 ` Kevin Traynor
2020-12-01 3:32 ` Kalesh Anakkur Purayil
2020-10-06 12:18 Kevin Traynor
2020-10-06 12:27 ` Slava Ovsiienko
2020-10-06 12:30 ` Kevin Traynor
2020-10-26 12:23 ` Chauskin, Igor
2020-11-05 9:19 ` Kevin Traynor
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=5d2fbe70-63fd-a965-c640-88f3eb936791@redhat.com \
--to=ktraynor@redhat.com \
--cc=oulijun@huawei.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).