patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Xueming Li <xuemingl@nvidia.com>
Cc: "dpdk stable" <stable@dpdk.org>,
	"Xueming Li" <xuemingl@nvidia.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	"Niklas Söderlund" <niklas.soderlund@corigine.com>,
	"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
	"Akhil Goyal" <gakhil@marvell.com>,
	"Alexander Kozyrev" <akozyrev@nvidia.com>,
	"Ankur Dwivedi" <adwivedi@marvell.com>,
	"Anoob Joseph" <anoobj@marvell.com>,
	"Bing Zhao" <bingz@nvidia.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	"Chaoyong He" <chaoyong.he@corigine.com>,
	"Dariusz Sosnowski" <dsosnowski@nvidia.com>,
	"Dengdui Huang" <huangdengdui@huawei.com>,
	"Gowrishankar Muthukrishnan" <gmuthukrishn@marvell.com>,
	"Harman Kalra" <hkalra@marvell.com>,
	"Huisong Li" <lihuisong@huawei.com>,
	"Jerin Jacob" <jerinj@marvell.com>,
	"Jie Hai" <haijie1@huawei.com>,
	"Junfeng Guo" <junfengg@nvidia.com>,
	"Kiran Kumar K" <kirankumark@marvell.com>,
	"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
	"Long Wu" <long.wu@corigine.com>,
	"Matan Azrad" <matan@nvidia.com>,
	"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
	"Ori Kam" <orika@nvidia.com>,
	"Pavan Nikhilesh" <pbhagavatula@marvell.com>,
	"Peng Zhang" <peng.zhang@corigine.com>,
	"Satha Rao" <skoteshwar@marvell.com>,
	"Shijith Thotton" <sthotton@marvell.com>,
	"Suanming Mou" <suanmingm@nvidia.com>,
	"Sunil Kumar Kori" <skori@marvell.com>,
	"Tejasree Kondoj" <ktejasree@marvell.com>,
	"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
	"Wathsala Vithanage" <wathsala.vithanage@arm.com>,
	"Zhirun Yan" <yanzhirun_163@163.com>
Subject: please help backporting some patches to stable release 23.11.5
Date: Thu, 26 Jun 2025 20:16:57 +0800	[thread overview]
Message-ID: <20250626121657.32689-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/15/25.

You can find the a temporary work-in-progress branch of the coming 23.11.5
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>

---
22252c56bf  Chaoyong He      net/nfp: standardize Rx descriptor endianness
99c065da47  Dengdui Huang    net/hns3: fix Rx packet without CRC data
cfefc94a8c  Gowrishankar Muthukrishnan crypto/cnxk: fix out-of-bounds access in SM2
82e0453609  Junfeng Guo      net/mlx5: fix template flow rule identification
98cf04bb90  Kiran Kumar K    test/graph: fix second run
f77eb8f3c6  Pavan Nikhilesh  event/cnxk: fix missing HW state checks
25e35296b5  Sunil Kumar Kori net/cnxk: fix reconfiguring MAC address

                 reply	other threads:[~2025-06-26 12:17 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=20250626121657.32689-1-xuemingl@nvidia.com \
    --to=xuemingl@nvidia.com \
    --cc=adwivedi@marvell.com \
    --cc=akozyrev@nvidia.com \
    --cc=anoobj@marvell.com \
    --cc=bingz@nvidia.com \
    --cc=bruce.richardson@intel.com \
    --cc=chaoyong.he@corigine.com \
    --cc=dsosnowski@nvidia.com \
    --cc=gakhil@marvell.com \
    --cc=gmuthukrishn@marvell.com \
    --cc=haijie1@huawei.com \
    --cc=hkalra@marvell.com \
    --cc=huangdengdui@huawei.com \
    --cc=humin29@huawei.com \
    --cc=jerinj@marvell.com \
    --cc=junfengg@nvidia.com \
    --cc=kirankumark@marvell.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=ktejasree@marvell.com \
    --cc=lihuisong@huawei.com \
    --cc=long.wu@corigine.com \
    --cc=matan@nvidia.com \
    --cc=ndabilpuram@marvell.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=orika@nvidia.com \
    --cc=pbhagavatula@marvell.com \
    --cc=peng.zhang@corigine.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=stable@dpdk.org \
    --cc=sthotton@marvell.com \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@nvidia.com \
    --cc=wathsala.vithanage@arm.com \
    --cc=xavier.huwei@huawei.com \
    --cc=yanzhirun_163@163.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).