From: huangdengdui <huangdengdui@huawei.com>
To: dpdk stable <stable@dpdk.org>, <xuemingl@nvidia.com>
Subject: Re: please help backporting some patches to stable release 22.11.3
Date: Tue, 20 Jun 2023 09:40:11 +0800 [thread overview]
Message-ID: <4748e0a6-6555-1aeb-685c-80d8b25f2deb@huawei.com> (raw)
In-Reply-To: <20230619022416.13730-1-xuemingl@nvidia.com>
Hi,
The "db42a84233 Dengdui Huang app/testpmd: fix crash with invalid queue"
no need to backport, because this patch depend on a new API in 23.07,
in addition, this bug has little impact.
On 2023/6/19 10:24, Xueming Li wrote:
> Hi commit authors (and maintainers),
>
> Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
> I didn't apply following commits from DPDK main to 22.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 22.11 branch, or
> - Indicate that the patch should not be backported
>
> Please do either of the above by 07/16/23.
>
> You can find the a temporary work-in-progress branch of the coming 22.11.3
> release at:
> https://git.dpdk.org/dpdk-stable/log/?h=22.11-staging
> 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 22.11] foo/bar: fix baz
>
> With git format-patch, this can be achieved by appending the parameter:
> --subject-prefix='PATCH 22.11'
>
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>
> FYI, branch 22.11 is located at tree:
> https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Xueming Li <xuemingl@nvidia.com>
>
> ---
> 925c27ec8d Chaoyong He net/nfp: fix offloading flows
> e97738919c Chaoyong He net/nfp: fix Tx descriptor free logic of NFD3
> db42a84233 Dengdui Huang app/testpmd: fix crash with invalid queue
> cd41a27154 Jie Hai net/hns3: get FEC capability from firmware
> 772e30281a Rahul Bhansali common/cnxk: fix CPT backpressure disable on LBK
> b37fe88a2c Srujana Challa event/cnxk: fix LMTST write for single event mode
> a37335bc62 Viacheslav Ovsiienko eal: choose IOVA mode according to compilation option
next parent reply other threads:[~2023-06-20 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230619022416.13730-1-xuemingl@nvidia.com>
2023-06-20 1:40 ` huangdengdui [this message]
2023-06-20 5:50 ` Xueming(Steven) Li
2023-08-10 0:06 Xueming Li
2023-08-11 14:24 ` Kishore Padmanabha
2023-08-15 13:02 ` Xueming(Steven) Li
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=4748e0a6-6555-1aeb-685c-80d8b25f2deb@huawei.com \
--to=huangdengdui@huawei.com \
--cc=stable@dpdk.org \
--cc=xuemingl@nvidia.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).