From: Xueming Li <xuemingl@nvidia.com>
Cc: <xuemingl@nvidia.com>, <stable@dpdk.org>,
Alex Vesker <valex@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Erez Shitrit <erezsh@nvidia.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Mark Bloch <mbloch@nvidia.com>, "Matan Azrad" <matan@nvidia.com>,
Mingjin Ye <mingjinx.ye@intel.com>, Ori Kam <orika@nvidia.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Suanming Mou <suanmingm@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: please help backporting some patches to stable release 23.11.1
Date: Tue, 5 Mar 2024 19:58:02 +0800 [thread overview]
Message-ID: <20240305115802.443162-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 03/15/24.
You can find the a temporary work-in-progress branch of the coming 23.11.1
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>
---
28e69588f4 Alex Vesker net/mlx5/hws: fix tunnel protocol checks
9f6186cf0d Mingjin Ye net/iavf: fix Rx/Tx burst in multi-process
next reply other threads:[~2024-03-05 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 11:58 Xueming Li [this message]
2024-04-13 13:12 ` Xueming 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=20240305115802.443162-1-xuemingl@nvidia.com \
--to=xuemingl@nvidia.com \
--cc=dsosnowski@nvidia.com \
--cc=erezsh@nvidia.com \
--cc=jingjing.wu@intel.com \
--cc=matan@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=mingjinx.ye@intel.com \
--cc=orika@nvidia.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=valex@nvidia.com \
--cc=viacheslavo@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).