From: Xueming Li <xuemingl@nvidia.com>
Cc: dpdk stable <stable@dpdk.org>, Harman Kalra <hkalra@marvell.com>,
"Kiran Kumar K" <kirankumark@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
"Sunil Kumar Kori" <skori@marvell.com>
Subject: please help backporting some patches to stable release 23.11.2
Date: Fri, 12 Jul 2024 19:08:22 +0800 [thread overview]
Message-ID: <20240712110822.310486-1-xuemingl@nvidia.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 23.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 23.11 branch, or
- Indicate that the patch should not be backported
Please do either of the above by 07/19/24.
You can find the a temporary work-in-progress branch of the coming 23.11.2
release at:
https://git.dpdk.org/dpdk-stable/log/?h=23.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 23.11] foo/bar: fix baz
With git format-patch, this can be achieved by appending the parameter:
--subject-prefix='PATCH 23.11'
Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
FYI, branch 23.11 is located at tree:
https://git.dpdk.org/dpdk-stable
Thanks.
Xueming Li <xuemingl@nvidia.com>
---
4c2f14bc6d Sunil Kumar Kori net/cnxk: fix xstats reset
next reply other threads:[~2024-07-12 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 11:08 Xueming Li [this message]
2024-08-12 13:10 ` Xueming Li
2024-08-14 2:40 ` Chaoyong He
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=20240712110822.310486-1-xuemingl@nvidia.com \
--to=xuemingl@nvidia.com \
--cc=hkalra@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).