patches for DPDK stable branches
 help / color / mirror / Atom feed
From: rongwei liu <rongweil@nvidia.com>
To: dpdk stable <stable@dpdk.org>, Luca Boccassi <luca.boccassi@gmail.com>
Subject: Re: please help backporting some patches to stable release 22.11.11
Date: Thu, 13 Nov 2025 03:06:07 +0000	[thread overview]
Message-ID: <DS0PR12MB84437CA6D8257A2E2A760460ABCDA@DS0PR12MB8443.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20251112165714.1618739-1-luca.boccassi@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4169 bytes --]

HI Luca:
                The below 2 patches are N/A for stable 22.11 branch.

112facb17b  Rongwei Liu      net/mlx5: fix meter mark allocation
3eec7a797f  Rongwei Liu      net/mlx5: remove counter alignment

BR
Rongwei Liu

From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
Date: Thursday, November 13, 2025 at 00:57
To: dpdk stable <stable@dpdk.org>
Cc: Alexander Kozyrev <akozyrev@nvidia.com>, Chengwen Feng <fengchengwen@huawei.com>, Ciara Power <ciara.power@intel.com>, Dariusz Sosnowski <dsosnowski@nvidia.com>, Ferruh Yigit <ferruh.yigit@intel.com>, Gagandeep Singh <g.singh@nxp.com>, Gavin Hu <gavin.hu@arm.com>, Geoff Thorpe <geoff.thorpe@nxp.com>, Gregory Etelson <getelson@nvidia.com>, Hemant Agrawal <hemant.agrawal@nxp.com>, Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>, Jerin Jacob <jerinj@marvell.com>, Jian Wang <jianwang@trustnetic.com>, Jiawen Wu <jiawenwu@trustnetic.com>, Keith Wiles <keith.wiles@intel.com>, Kiran Kumar K <kirankumark@marvell.com>, Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>, Maayan Kashani <mkashani@nvidia.com>, Matan Azrad <matan@nvidia.com>, Michael Baum <michaelba@nvidia.com>, Nithin Dabilpuram <ndabilpuram@marvell.com>, Ola Liljedahl <ola.liljedahl@arm.com>, Phil Yang <phil.yang@arm.com>, rongwei liu <rongweil@nvidia.com>, Roy Pledge <roy.pledge@nxp.com>, Ruifeng Wang <ruifeng.wang@arm.com>, Sachin Saxena <sachin.saxena@nxp.com>, Satha Rao <skoteshwar@marvell.com>, Satheesh Paul <psatheesh@marvell.com>, Shreyansh Jain <shreyansh.jain@nxp.com>, Steve Capper <steve.capper@arm.com>, Sunil Kumar Kori <skori@marvell.com>, Slava Ovsiienko <viacheslavo@nvidia.com>, Wathsala Vithanage <wathsala.vithanage@arm.com>, Xueming Li <xuemingl@nvidia.com>
Subject: please help backporting some patches to stable release 22.11.11
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 2025/11/19.

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

---
0e3c389b9e  Gagandeep Singh  bus/dpaa: do proper cleanup of frame queues on shutdown
d524b58819  Gregory Etelson  net/mlx5: fix external queues access
6280a30607  Jiawen Wu        net/ngbe: fix checksum error counter
b9ad8a6e72  Jiawen Wu        net/txgbe: fix checksum error counter
17082f45e9  Maayan Kashani   net/mlx5: fix modify field action restriction
112facb17b  Rongwei Liu      net/mlx5: fix meter mark allocation
3eec7a797f  Rongwei Liu      net/mlx5: remove counter alignment
d762a8fbbd  Satheesh Paul    net/cnxk: fix port ID default action
3bf9f0f9f0  Viacheslav Ovsiienko net/mlx5: fix control flow leakage for external SQ
8357af1cb3  Wathsala Vithanage mcslock: fix memory ordering
66d5f96278  Wathsala Vithanage ring: establish safe partial order in HTS mode
36b69b5f95  Wathsala Vithanage ring: establish safe partial order in RTS mode

[-- Attachment #2: Type: text/html, Size: 8222 bytes --]

  reply	other threads:[~2025-11-13  3:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 16:57 luca.boccassi
2025-11-13  3:06 ` rongwei liu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-27 16:24 luca.boccassi
2025-10-28 10:50 ` Nicolau, Radu
2025-10-29 10:56 ` Loftus, Ciara
2025-10-31 13:48   ` Kevin Traynor
2025-11-03 10:20     ` Loftus, Ciara
2025-11-03 10:25       ` Kevin Traynor
2025-10-29 14:29 ` David Marchand
2025-11-02  9:43 ` Gregory Etelson
2025-11-12 11:52 ` Slava Ovsiienko

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=DS0PR12MB84437CA6D8257A2E2A760460ABCDA@DS0PR12MB8443.namprd12.prod.outlook.com \
    --to=rongweil@nvidia.com \
    --cc=luca.boccassi@gmail.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).