patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: dpdk stable <stable@dpdk.org>
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Hanumanth Pothula <hpothula@marvell.com>,
	Harman Kalra <hkalra@marvell.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Nicolas Chautru <nicolas.chautru@intel.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Shijith Thotton <sthotton@marvell.com>,
	Steve Yang <stevex.yang@intel.com>,
	Yogesh Jangra <yogesh.jangra@intel.com>
Subject: please help backporting some patches to stable release 21.11.3
Date: Wed, 30 Nov 2022 10:02:09 +0000	[thread overview]
Message-ID: <20221130100209.508891-1-ktraynor@redhat.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 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 12/02/22. After that validation will be
beginning and they will not be considered for backport until 21.11.4.

You can find the a temporary work-in-progress branch of the coming 21.11.3
release at:
    https://github.com/kevintraynor/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 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 "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 21.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Kevin

---
5a0f64d84b  Hanumanth Pothula net/cnxk: fix configuring large Rx/Tx queues
59ceaa72d5  Harman Kalra     common/cnxk: fix part number for CN10K
e77d682aad  Nicolas Chautru  baseband/acc100: fix input error related to padding
5781638519  Nithin Dabilpuram common/cnxk: fix RQ mask config for CN10KB chip
3fe71706ab  Pavan Nikhilesh  event/cnxk: fix stale data in workslot
927cb43fe9  Pavan Nikhilesh  examples/l3fwd: fix port group mask with AltiVec
0f044b6681  Steve Yang       net/iavf: fix refine protocol header
0b241667cc  Steve Yang       net/iavf: fix tainted scalar
b125c0e721  Steve Yang       net/iavf: fix tainted scalar
a774cba0bb  Yogesh Jangra    pipeline: fix validate header instruction


             reply	other threads:[~2022-11-30 10:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 10:02 Kevin Traynor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-23 18:06 Kevin Traynor
2022-11-24  8:01 ` Michael Baum
2022-11-24 17:02 ` Ji, Kai
2022-11-29 12:55   ` Kevin Traynor
2022-11-28  9:24 ` Spike Du
2022-11-29 12:59   ` Kevin Traynor
2022-11-28  9:28 ` Shun Hao
2022-11-29 13:06   ` Kevin Traynor
2022-11-30  8:18 ` lihuisong (C)
2022-11-30  9:51   ` Kevin Traynor
2022-12-09  6:06     ` Jiang, YuX
2022-11-11 18:44 Kevin Traynor
2022-10-25 15:35 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:
  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=20221130100209.508891-1-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=hkalra@marvell.com \
    --cc=hpothula@marvell.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=ndabilpuram@marvell.com \
    --cc=nicolas.chautru@intel.com \
    --cc=pbhagavatula@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=stable@dpdk.org \
    --cc=stevex.yang@intel.com \
    --cc=sthotton@marvell.com \
    --cc=yogesh.jangra@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).