DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
* please help backporting some patches to stable release 24.11.9
@ 2026-11-16 23:00 luca.boccassi
  0 siblings, 0 replies; 2+ messages in thread
From: luca.boccassi @ 2026-11-16 23:00 UTC (permalink / raw)
  To: dpdk stable
  Cc: dev, Anatoly Burakov, Anurag Mandal, Bing Zhao, Bruce Richardson,
	Ciara Loftus, Dariusz Sosnowski, Kevin Bowling, Matan Azrad,
	Ori Kam, Soumyadeep Hore, Suanming Mou, Thomas Monjalon,
	Viacheslav Ovsiienko

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 24.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 24.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 2026/11/23.

You can find the a temporary work-in-progress branch of the coming 24.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 24.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 24.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 24.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Luca Boccassi

---
5e45dcdf1e  Anatoly Burakov  net/iavf: allow flow validation without engine callback
7810fe8de3  Bing Zhao        net/mlx5/hws: fix eCPRI flow matching in strict mode
485360e1e8  Ciara Loftus     net/iavf: fix crash in Tx drain on PF reset
36f9648dde  Kevin Bowling    net/iavf: fix AdminQ polling after interrupt setup failure

^ permalink raw reply	[flat|nested] 2+ messages in thread
* please help backporting some patches to stable release 24.11.9
@ 2026-11-05 17:20 luca.boccassi
  0 siblings, 0 replies; 2+ messages in thread
From: luca.boccassi @ 2026-11-05 17:20 UTC (permalink / raw)
  To: dpdk stable
  Cc: dev, Akhil Goyal, Anatoly Burakov, Andrew Rybchenko, Anoob Joseph,
	Anurag Mandal, Bruce Richardson, Chengwen Feng, Ciara Loftus,
	David Marchand, Erik Gabriel Carrillo, Ferruh Yigit,
	Gagandeep Singh, Geoff Thorpe, Harman Kalra, Hemant Agrawal,
	Jun Yang, mb, Ori Kam, Qiming Yang, Qi Zhang, Rohit Raj,
	Roy Pledge, Sachin Saxena, Shaiq Wani, Shreyansh Jain,
	Stephen Hemminger, Thomas Monjalon, Tyler Retzlaff,
	Volodymyr Fialko

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 24.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 24.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 2026-11-10.

You can find the a temporary work-in-progress branch of the coming 24.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 24.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 24.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 24.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Luca Boccassi

---
c8325b3939  Anatoly Burakov  ethdev: fix MACsec item support in flow conversion
b1ebf0fc1b  Anatoly Burakov  net/iavf: centralize memory management for flows
7495d45fb2  David Marchand   bus/fslmc: fix interrupt leak in DPIO cleanup
0e03411639  David Marchand   test: defer timer initialization
dd82d0e9c4  Jun Yang         bus/dpaa: fix hang on FQ shutdown
a5dd495b8e  Shaiq Wani       net/intel: fix idpf Tx payload corruption in split queue
670ead3dd1  Stephen Hemminger eal/linux: fix FD leak in alarm subsystem
8c8da52f31  Thomas Monjalon  eal: enforce internal API check with Clang 14

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-11-16 23:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-16 23:00 please help backporting some patches to stable release 24.11.9 luca.boccassi
  -- strict thread matches above, loose matches on Subject: below --
2026-11-05 17:20 luca.boccassi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox