patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: "Bruce Richardson" <bruce.richardson@intel.com>,
	"Chaoyong He" <chaoyong.he@corigine.com>,
	"Ciara Loftus" <ciara.loftus@intel.com>,
	"Ferruh Yigit" <ferruh.yigit@amd.com>,
	"Frank Du" <frank.du@intel.com>,
	"Ian Stokes" <ian.stokes@intel.com>,
	"Jacob Keller" <jacob.e.keller@intel.com>,
	"Kevin Laatz" <kevin.laatz@intel.com>,
	"Kiran Kumar K" <kirankumark@marvell.com>,
	"Long Wu" <long.wu@corigine.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Niklas Söderlund" <niklas.soderlund@corigine.com>,
	"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
	"Paul M Stillwell Jr" <paul.m.stillwell.jr@intel.com>,
	"Peng Zhang" <peng.zhang@corigine.com>,
	"Qiming Yang" <qiming.yang@intel.com>,
	"Qi Zhang" <qi.z.zhang@intel.com>,
	"Rahul Bhansali" <rbhansali@marvell.com>,
	"Ray Kinsella" <mdr@ashroe.eu>,
	"Satha Rao" <skoteshwar@marvell.com>,
	"Satheesh Paul" <psatheesh@marvell.com>,
	"Sunil Kumar Kori" <skori@marvell.com>,
	"Xiaolong Ye" <xiaolong.ye@intel.com>
Subject: please help backporting some patches to stable release 22.11.6
Date: Mon, 15 Jul 2024 16:32:59 +0100	[thread overview]
Message-ID: <20240715153259.2231242-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 07/22/24.

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

---
97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF representor port
fde2a1cb34  Rahul Bhansali   net/cnxk: postpone disabling NPC Rx and MCAM

             reply	other threads:[~2024-07-15 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 15:32 luca.boccassi [this message]
     [not found] ` <PH0PR11MB477576B152FD2BAAD2D9B97580A22@PH0PR11MB4775.namprd11.prod.outlook.com>
2024-07-16 10:30   ` Luca Boccassi
2024-07-17  1:57     ` Du, Frank
  -- strict thread matches above, loose matches on Subject: below --
2024-07-24 11:36 luca.boccassi
2024-07-24 17:42 ` Stephen Hemminger
2024-06-25  0:04 luca.boccassi

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=20240715153259.2231242-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=chaoyong.he@corigine.com \
    --cc=ciara.loftus@intel.com \
    --cc=ferruh.yigit@amd.com \
    --cc=frank.du@intel.com \
    --cc=ian.stokes@intel.com \
    --cc=jacob.e.keller@intel.com \
    --cc=kevin.laatz@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=long.wu@corigine.com \
    --cc=mb@smartsharesystems.com \
    --cc=mdr@ashroe.eu \
    --cc=ndabilpuram@marvell.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=paul.m.stillwell.jr@intel.com \
    --cc=peng.zhang@corigine.com \
    --cc=psatheesh@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=rbhansali@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=stable@dpdk.org \
    --cc=xiaolong.ye@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).