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>,
	"Alexander Kozyrev" <akozyrev@nvidia.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Bing Zhao <bingz@nvidia.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	"Ciara Power" <ciara.power@intel.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Ferruh Yigit <ferruh.yigit@amd.com>, Gavin Li <gavinl@nvidia.com>,
	Ian Stokes <ian.stokes@intel.com>,
	Keith Wiles <keith.wiles@intel.com>,
	Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Qiming Yang <qiming.yang@intel.com>,
	Robin Jarry <rjarry@redhat.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	"Suanming Mou" <suanmingm@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	 "Viacheslav Ovsiienko" <viacheslavo@nvidia.com>
Subject: please help backporting some patches to stable release 23.11.3
Date: Mon, 11 Nov 2024 14:54:25 +0800	[thread overview]
Message-ID: <20241111065425.223357-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 11/30/24.

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

---
b0bad8e998  Anatoly Burakov  net/i40e/base: fix setting MAC type for X722
e4a4087992  Gavin Li         net/mlx5: set errno for ipool allocation failures
6f96937dad  Robin Jarry      ethdev: fix race on ports in telemetry endpoints

             reply	other threads:[~2024-11-11  6:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11  6:54 Xueming Li [this message]
2024-11-11 11:44 ` Robin Jarry
2024-12-06 13:30   ` Xueming Li
2024-12-07  8:20 ` Xueming Li
2024-12-09 15:56   ` [PATCH 23.11] rcu: fix implicit conversion in bit shift Andre Muezerie
2024-12-10 14:29     ` Xueming Li

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=20241111065425.223357-1-xuemingl@nvidia.com \
    --to=xuemingl@nvidia.com \
    --cc=akozyrev@nvidia.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bingz@nvidia.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dsosnowski@nvidia.com \
    --cc=ferruh.yigit@amd.com \
    --cc=gavinl@nvidia.com \
    --cc=ian.stokes@intel.com \
    --cc=keith.wiles@intel.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=rjarry@redhat.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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).