patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <>
To: dpdk stable <>
Cc: Dariusz Sosnowski <>,
	Gagandeep Singh <>, Matan Azrad <>,
	Michael Baum <>,
	Viacheslav Ovsiienko <>
Subject: please help backporting some patches to stable release 21.11.2
Date: Tue, 10 May 2022 14:00:03 +0100
Message-ID: <> (raw)

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/
I didn't apply following commits from DPDK main to 21.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 21.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 05/17/22.

You can find the a temporary work-in-progress branch of the coming 21.11.2
release at:
It is recommended to backport on top of that to minimize further conflicts or

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:

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 21.11] foo/bar: fix baz

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

Send the backported patch to "" but not "".

FYI, branch 21.11 is located at tree:



d2fa2632a4  Dariusz Sosnowski net/mlx5: fix RSS hash types adjustment
13ce268103  Gagandeep Singh  common/dpaax: remove dead code
7a99336865  Michael Baum     net/mlx5: fix LRO configuration in drop Rx queue
a213b86821  Michael Baum     net/mlx5: fix LRO validation in Rx setup

             reply	other threads:[~2022-05-10 13:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 13:00 Kevin Traynor [this message]
2022-06-21 10:02 Kevin Traynor
2022-06-22  2:57 ` Jiawen Wu
2022-06-22  4:26 ` Gagandeep Singh
2022-06-23 14:08   ` Kevin Traynor
2022-06-22  4:47 ` Zhou, YidingX
2022-06-22  8:40   ` Kalesh Anakkur Purayil
2022-06-22 10:48 ` Niklas Söderlund
2022-06-24 14:17   ` Kevin Traynor
     [not found] ` <>
2022-06-23 14:05   ` Kevin Traynor
2022-06-24 16:31 Kevin Traynor

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ \
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone