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>,
	"Paul E. McKenney" <paulmck@linux.ibm.com>,
	"Ajit Khaparde" <ajit.khaparde@broadcom.com>,
	"Andre Muezerie" <andremue@linux.microsoft.com>,
	"Bing Zhao" <bingz@nvidia.com>,
	"Dariusz Sosnowski" <dsosnowski@nvidia.com>,
	"Gregory Etelson" <getelson@nvidia.com>,
	"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
	"Kishore Padmanabha" <kishore.padmanabha@broadcom.com>,
	"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
	"Matan Azrad" <matan@nvidia.com>,
	"Mike Baucom" <michael.baucom@broadcom.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Ola Liljedahl" <ola.liljedahl@arm.com>,
	"Ori Kam" <orika@nvidia.com>,
	"Shahaji Bhosle" <sbhosle@broadcom.com>,
	"Shuanglin Wang" <shuanglin.wang@broadcom.com>,
	"Somnath Kotur" <somnath.kotur@broadcom.com>,
	"Sriharsha Basavapatna" <sriharsha.basavapatna@broadcom.com>,
	"Steve Capper" <steve.capper@arm.com>,
	"Suanming Mou" <suanmingm@nvidia.com>,
	"Venkat Duvvuru" <venkatkumar.duvvuru@broadcom.com>,
	"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
	"Xiaoyu Min" <jackmin@nvidia.com>
Subject: please help backporting some patches to stable release 23.11.3
Date: Sat, 7 Dec 2024 16:20:33 +0800	[thread overview]
Message-ID: <20241207082033.489453-1-xuemingl@nvidia.com> (raw)
In-Reply-To: <20241111065425.223357-1-xuemingl@nvidia.com>

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/10/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>

---
ffe827f38e  Andre Muezerie   rcu: fix implicit conversion in bit shift
d46f3b525a  Gregory Etelson  net/mlx5: fix error notifications in counter initialization
8782e4de3e  Kishore Padmanabha net/bnxt/tf_ulp: fix parent child DB counters

  parent reply	other threads:[~2024-12-07  8:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11  6:54 Xueming Li
2024-11-11 11:44 ` Robin Jarry
2024-12-06 13:30   ` Xueming Li
2024-12-07  8:20 ` Xueming Li [this message]
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=20241207082033.489453-1-xuemingl@nvidia.com \
    --to=xuemingl@nvidia.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=andremue@linux.microsoft.com \
    --cc=bingz@nvidia.com \
    --cc=dsosnowski@nvidia.com \
    --cc=getelson@nvidia.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jackmin@nvidia.com \
    --cc=kishore.padmanabha@broadcom.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=matan@nvidia.com \
    --cc=mb@smartsharesystems.com \
    --cc=michael.baucom@broadcom.com \
    --cc=ola.liljedahl@arm.com \
    --cc=orika@nvidia.com \
    --cc=paulmck@linux.ibm.com \
    --cc=sbhosle@broadcom.com \
    --cc=shuanglin.wang@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=sriharsha.basavapatna@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=steve.capper@arm.com \
    --cc=suanmingm@nvidia.com \
    --cc=venkatkumar.duvvuru@broadcom.com \
    --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).