From: Shani Peretz <shperetz@nvidia.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
dpdk stable <stable@dpdk.org>
Subject: RE: please help backporting some patches to stable release 23.11.6
Date: Tue, 23 Dec 2025 08:27:55 +0000 [thread overview]
Message-ID: <MW4PR12MB74840B1276C8DE176491BF62BFB5A@MW4PR12MB7484.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DS0PR11MB7309E3A0E6E6EE32CC2517CA97B4A@DS0PR11MB7309.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Richardson, Bruce <bruce.richardson@intel.com>
> Sent: Monday, 22 December 2025 10:42
> To: dpdk stable <stable@dpdk.org>
> Subject: RE: please help backporting some patches to stable release 23.11.6
>
> External email: Use caution opening links or attachments
>
>
> > -----Original Message-----
> > From: Shani Peretz <shperetz@nvidia.com>
> > Sent: Sunday, December 21, 2025 4:26 PM
> > Cc: Burakov, Anatoly <anatoly.burakov@intel.com>; Andrew Rybchenko
> > <andrew.rybchenko@oktetlabs.ru>; Ankit Garg <nktgrg@google.com>;
> > Richardson, Bruce <bruce.richardson@intel.com>; Chengwen Feng
> > <fengchengwen@huawei.com>; Loftus, Ciara <ciara.loftus@intel.com>;
> > Cunming Liang <cunming.liang@intel.com>; Dariusz Sosnowski
> > <dsosnowski@nvidia.com>; Marchand, David
> <david.marchand@redhat.com>;
> > Gagandeep Singh <g.singh@nxp.com>; Haiyue Wang
> > <haiyue.wang@intel.com>; Hemant Agrawal <hemant.agrawal@nxp.com>;
> > Nagarahalli, Honnappa <Honnappa.Nagarahalli@arm.com>; Jasper Tran
> > O'Leary <jtranoleary@google.com>; Jeroen de Borst
> > <jeroendb@google.com>; Joshua Washington <joshwash@google.com>;
> > Junfeng Guo <junfengg@nvidia.com>; Konstantin Ananyev
> > <konstantin.v.ananyev@yandex.ru>; Matan Azrad <matan@nvidia.com>;
> > Michael Baum <michaelba@nvidia.com>; Morten Brørup
> > <mb@smartsharesystems.com>; Nawal Kishor <nkishor@marvell.com>; Ori
> > Kam <orika@nvidia.com>; Robin Jarry <rjarry@redhat.com>; Rongwei Liu
> > <rongweil@nvidia.com>; Rushil Gupta <rushilg@google.com>; Sachin
> > Saxena <sachin.saxena@nxp.com>; Gobriel, Sameh
> > <sameh.gobriel@intel.com>; Shreyansh Jain <shreyansh.jain@nxp.com>;
> > Suanming Mou <suanmingm@nvidia.com>; Thomas Monjalon
> > <thomas@monjalon.net>; Vamsi Attunuru <vattunuru@marvell.com>;
> > Viacheslav Ovsiienko <viacheslavo@nvidia.com>; Medvedkin, Vladimir
> > <vladimir.medvedkin@intel.com>; Xiaoyun Li <xiaoyun.li@intel.com>;
> > Wang, Yipeng1 <yipeng1.wang@intel.com>; Zhe Tao <zhe.tao@intel.com>
> > Subject: please help backporting some patches to stable release
> > 23.11.6
> >
> > 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 12/28/25.
> >
> > You can find the a temporary work-in-progress branch of the coming
> > 23.11.6 release at:
> > https://github.com/shanipr/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 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.
> >
> > Shani
> >
> > ---
> > b74d638ab9 Bruce Richardson test/func_reentrancy: fix args to EAL
> > init call
>
> Since this is a patch to unit tests only, and hasn't been causing us any issues
> before, I don't think we need it backported.
>
> /Bruce
Thanks Bruce, will remove from need backport list
next prev parent reply other threads:[~2025-12-23 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251221162621.929312-1-shperetz@nvidia.com>
2025-12-22 8:42 ` Richardson, Bruce
2025-12-23 8:27 ` Shani Peretz [this message]
2025-12-23 8:24 Shani Peretz
2025-12-23 8:26 ` Shani Peretz
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=MW4PR12MB74840B1276C8DE176491BF62BFB5A@MW4PR12MB7484.namprd12.prod.outlook.com \
--to=shperetz@nvidia.com \
--cc=bruce.richardson@intel.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).