From: Xueming Li <xuemingl@nvidia.com>
Cc: xuemingl@nvidia.com, "dpdk stable" <stable@dpdk.org>,
"Niklas Söderlund" <niklas.soderlund@corigine.com>,
"Chaoyong He" <chaoyong.he@corigine.com>,
"Daniel Mrzyglod" <danielx.t.mrzyglod@intel.com>,
"James Hershaw" <james.hershaw@corigine.com>,
"Jeroen de Borst" <jeroendb@google.com>,
"John McNamara" <john.mcnamara@intel.com>,
"Joshua Washington" <joshwash@google.com>,
"Junfeng Guo" <junfeng.guo@intel.com>,
"Kirill Rybalchenko" <kirill.rybalchenko@intel.com>,
"Lingli Chen" <linglix.chen@intel.com>,
"Long Wu" <long.wu@corigine.com>,
"Pablo de Lara" <pablo.de.lara.guarch@intel.com>,
"Praveen Kaligineedi" <pkaligineedi@google.com>,
"Raslan Darawsheh" <rasland@nvidia.com>,
"Rushil Gupta" <rushilg@google.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Xiaoyun Li" <xiaoyun.li@intel.com>
Subject: please help backporting some patches to stable release 23.11.4
Date: Tue, 18 Feb 2025 20:46:12 +0800 [thread overview]
Message-ID: <20250218124612.42412-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/25.
You can find the a temporary work-in-progress branch of the coming 23.11.4
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>
---
d4831cc5c6 Lingli Chen doc: add two more tested Intel NICs in 24.11
c43d2aab42 Long Wu net/nfp: fix VF link speed
a71168a775 Praveen Kaligineedi net/gve: allocate Rx QPL pages using malloc
2ac64b2c43 Raslan Darawsheh doc: add tested platforms with NVIDIA NICs in 24.11
19630bd0d7 Stephen Hemminger examples/ptpclient: fix message parsing
reply other threads:[~2025-02-18 12:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250218124612.42412-1-xuemingl@nvidia.com \
--to=xuemingl@nvidia.com \
--cc=chaoyong.he@corigine.com \
--cc=danielx.t.mrzyglod@intel.com \
--cc=james.hershaw@corigine.com \
--cc=jeroendb@google.com \
--cc=john.mcnamara@intel.com \
--cc=joshwash@google.com \
--cc=junfeng.guo@intel.com \
--cc=kirill.rybalchenko@intel.com \
--cc=linglix.chen@intel.com \
--cc=long.wu@corigine.com \
--cc=niklas.soderlund@corigine.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pkaligineedi@google.com \
--cc=rasland@nvidia.com \
--cc=rushilg@google.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=xiaoyun.li@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).