patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Alexander Kozyrev <akozyrev@nvidia.com>,
	Aman Singh <aman.deep.singh@intel.com>,
	Bing Zhao <bingz@mellanox.com>, Bing Zhao <bingz@nvidia.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Gregory Etelson <getelson@nvidia.com>,
	Hailin Xu <hailinx.xu@intel.com>,
	Jingjing Wu <jingjing.wu@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@huawei.com>,
	Maayan Kashani <mkashani@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,
	Nupur Uttarwar <nuttarwar@nvidia.com>,
	Qiming Yang <qiming.yang@intel.com>,
	Sivaprasad Tummala <sivaprasad.tummala@amd.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Tomasz Kulasek <tomaszx.kulasek@intel.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	Xiaoyun Li <xiaoyun.li@intel.com>,
	Yuying Zhang <yuying.zhang@intel.com>
Subject: please help backporting some patches to stable release 22.11.11
Date: Thu, 20 Nov 2025 12:53:30 +0000	[thread overview]
Message-ID: <20251120125332.758920-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 2025/11/28.

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

---
bd96307d15  Bruce Richardson net/fm10k: fix Tx packet prepare
19d7188f6f  Bruce Richardson net/ixgbe: fix Tx packet prepare
39454e245b  Maayan Kashani   app/testpmd: fix flex item link parsing
860f6c63db  Maayan Kashani   net/mlx5: fix device start error handling
327682174e  Nupur Uttarwar   net/mlx5: skip Rx control flow tables in isolated mode
750f635fc6  Sivaprasad Tummala net/mlx5: fix spurious CPU wakeups
743bbd3bd2  Sunil Kumar Kori net/ice: fix Tx packet prepare

             reply	other threads:[~2025-11-20 12:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 12:53 luca.boccassi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-12 16:57 luca.boccassi
2025-11-13  3:06 ` rongwei liu
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=20251120125332.758920-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=akozyrev@nvidia.com \
    --cc=aman.deep.singh@intel.com \
    --cc=bingz@mellanox.com \
    --cc=bingz@nvidia.com \
    --cc=bruce.richardson@intel.com \
    --cc=dsosnowski@nvidia.com \
    --cc=ferruh.yigit@intel.com \
    --cc=getelson@nvidia.com \
    --cc=hailinx.xu@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=konstantin.ananyev@huawei.com \
    --cc=matan@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=nuttarwar@nvidia.com \
    --cc=qiming.yang@intel.com \
    --cc=sivaprasad.tummala@amd.com \
    --cc=skori@marvell.com \
    --cc=stable@dpdk.org \
    --cc=tomaszx.kulasek@intel.com \
    --cc=viacheslavo@nvidia.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=xiaoyun.li@intel.com \
    --cc=yuying.zhang@intel.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).