From: Kevin Traynor <ktraynor@redhat.com>
To: dpdk stable <stable@dpdk.org>
Cc: Abdullah Sevincer <abdullah.sevincer@intel.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Chenbo Xia <chenbo.xia@intel.com>,
David Marchand <david.marchand@redhat.com>,
Dongdong Liu <liudongdong3@huawei.com>,
Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
Gagandeep Singh <g.singh@nxp.com>,
Hanumanth Pothula <hpothula@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
Harry van Haaren <harry.van.haaren@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Huisong Li <lihuisong@huawei.com>,
Kevin Liu <kevinx.liu@intel.com>,
Mao YingMing <maoyingming@baidu.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Qiming Yang <qiming.yang@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Sunil Kumar Kori <skori@marvell.com>,
Wei Ling <weix.ling@intel.com>, Wenwu Ma <wenwux.ma@intel.com>
Subject: please help backporting some patches to stable release 21.11.3
Date: Tue, 25 Oct 2022 16:35:21 +0100 [thread overview]
Message-ID: <20221025153521.145285-1-ktraynor@redhat.com> (raw)
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 21.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 21.11 branch, or
- Indicate that the patch should not be backported
Please do either of the above by 11/01/22.
You can find the a temporary work-in-progress branch of the coming 21.11.3
release at:
https://github.com/kevintraynor/dpdk-stable
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 21.11] foo/bar: fix baz
With git format-patch, this can be achieved by appending the parameter:
--subject-prefix='PATCH 21.11'
Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
FYI, branch 21.11 is located at tree:
https://git.dpdk.org/dpdk-stable
Thanks.
Kevin
---
9c9e72326b Abdullah Sevincer event/dlb2: handle enqueuing more than maximum depth
d4cbbee345 David Marchand trace: fix metadata dump
329280c53e Erik Gabriel Carrillo service: fix early move to inactive status
b0074a7ba1 Gagandeep Singh net/dpaa2: fix buffer freeing on SG Tx
8716c0ec06 Gagandeep Singh net/dpaa: fix buffer freeing on SG Tx
5a0f64d84b Hanumanth Pothula net/cnxk: fix configuring large Rx/Tx queues
59ceaa72d5 Harman Kalra common/cnxk: fix part number for CN10K
1042ed401f Huisong Li net/hns3: fix restore filter function input
0d81da2559 Huisong Li net/hns3: fix RSS rule restore
4bfb499829 Mao YingMing net/bnxt: fix null pointer dereference in LED config
3fe71706ab Pavan Nikhilesh event/cnxk: fix stale data in workslot
b0472e210f Qi Zhang net/ice/base: fix input set of GTPoGRE
40abb903fe Wenwu Ma examples/vhost: fix use after free
next reply other threads:[~2022-10-25 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 15:35 Kevin Traynor [this message]
2022-11-11 18:44 Kevin Traynor
2022-11-23 18:06 Kevin Traynor
2022-11-24 8:01 ` Michael Baum
2022-11-24 17:02 ` Ji, Kai
2022-11-29 12:55 ` Kevin Traynor
2022-11-28 9:24 ` Spike Du
2022-11-29 12:59 ` Kevin Traynor
2022-11-28 9:28 ` Shun Hao
2022-11-29 13:06 ` Kevin Traynor
2022-11-30 8:18 ` lihuisong (C)
2022-11-30 9:51 ` Kevin Traynor
2022-12-09 6:06 ` Jiang, YuX
2022-11-30 10:02 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=20221025153521.145285-1-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=abdullah.sevincer@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=erik.g.carrillo@intel.com \
--cc=g.singh@nxp.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=hkalra@marvell.com \
--cc=hpothula@marvell.com \
--cc=kevinx.liu@intel.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=maoyingming@baidu.com \
--cc=pbhagavatula@marvell.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=skori@marvell.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=weix.ling@intel.com \
--cc=wenwux.ma@intel.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).