From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: "Akhil Goyal" <gakhil@marvell.com>,
"Alejandro Lucero" <alejandro.lucero@netronome.com>,
"Chaoyong He" <chaoyong.he@corigine.com>,
"David Marchand" <david.marchand@redhat.com>,
"Dengdui Huang" <huangdengdui@huawei.com>,
"Dongdong Liu" <liudongdong3@huawei.com>,
"Fan Zhang" <fanzhang.oss@gmail.com>,
"Hailin Xu" <hailinx.xu@intel.com>,
"Huisong Li" <lihuisong@huawei.com>,
"Jay Zhou" <jianjay.zhou@huawei.com>,
"Jerin Jacob" <jerinj@marvell.com>,
"Jie Hai" <haijie1@huawei.com>,
"Kaiwen Deng" <kaiwenx.deng@intel.com>,
"Kiran Kumar K" <kirankumark@marvell.com>,
"Long Wu" <long.wu@corigine.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
"Niklas Söderlund" <niklas.soderlund@corigine.com>,
"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
"Pavan Nikhilesh" <pbhagavatula@marvell.com>,
"Peng Zhang" <peng.zhang@corigine.com>,
"Rajesh Mudimadugula" <rmudimadugul@marvell.com>,
"Rolf Neugebauer" <rolf.neugebauer@netronome.com>,
"Ruifeng Wang" <ruifeng.wang@arm.com>,
"Satha Rao" <skoteshwar@marvell.com>,
"Shijith Thotton" <sthotton@marvell.com>,
"Sunil Kumar Kori" <skori@marvell.com>,
"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
"Wei Zhao" <wei.zhao1@intel.com>,
"Wenzhuo Lu" <wenzhuo.lu@intel.com>,
"Yisen Zhuang" <yisen.zhuang@huawei.com>
Subject: please help backporting some patches to stable release 22.11.9
Date: Thu, 12 Jun 2025 22:15:56 +0100 [thread overview]
Message-ID: <20250612211558.2507813-1-luca.boccassi@gmail.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 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 06/19/25.
You can find the a temporary work-in-progress branch of the coming 22.11.9
release at:
https://github.com/bluca/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 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.
Luca Boccassi
---
53df26286e Chaoyong He net/nfp: fix crash with null RSS hash key
346a007e16 Chaoyong He net/nfp: fix hash key length logic
7c37826c2b David Marchand test/lcore: fix race in per-lcore test
99c065da47 Dengdui Huang net/hns3: fix Rx packet without CRC data
09766f41b3 Kaiwen Deng net/ixgbe: enable ethertype filter for E610
98cf04bb90 Kiran Kumar K test/graph: fix second run
f77eb8f3c6 Pavan Nikhilesh event/cnxk: fix missing HW state checks
9843181aa5 Rajesh Mudimadugula crypto/virtio: fix driver ID
25e35296b5 Sunil Kumar Kori net/cnxk: fix reconfiguring MAC address
reply other threads:[~2025-06-12 21:16 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=20250612211558.2507813-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=alejandro.lucero@netronome.com \
--cc=chaoyong.he@corigine.com \
--cc=david.marchand@redhat.com \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=haijie1@huawei.com \
--cc=hailinx.xu@intel.com \
--cc=huangdengdui@huawei.com \
--cc=humin29@huawei.com \
--cc=jerinj@marvell.com \
--cc=jianjay.zhou@huawei.com \
--cc=kaiwenx.deng@intel.com \
--cc=kirankumark@marvell.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=long.wu@corigine.com \
--cc=ndabilpuram@marvell.com \
--cc=niklas.soderlund@corigine.com \
--cc=pbhagavatula@marvell.com \
--cc=peng.zhang@corigine.com \
--cc=rmudimadugul@marvell.com \
--cc=rolf.neugebauer@netronome.com \
--cc=ruifeng.wang@arm.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=stable@dpdk.org \
--cc=sthotton@marvell.com \
--cc=wei.zhao1@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=xavier.huwei@huawei.com \
--cc=yisen.zhuang@huawei.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).