patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: "Aman Singh" <aman.deep.singh@intel.com>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
	"Beilei Xing" <beilei.xing@intel.com>,
	"Bing Zhao" <bingz@nvidia.com>,
	"Chengwen Feng" <fengchengwen@huawei.com>,
	"Cristian Dumitrescu" <cristian.dumitrescu@intel.com>,
	"Dariusz Sosnowski" <dsosnowski@nvidia.com>,
	"Dengdui Huang" <huangdengdui@huawei.com>,
	"Dmitry Kozlyuk" <dmitry.kozliuk@gmail.com>,
	"Ferruh Yigit" <ferruh.yigit@amd.com>,
	"Hongbo Li" <hongbox.li@intel.com>,
	"Jerin Jacob" <jerinj@marvell.com>,
	"Jingjing Wu" <jingjing.wu@intel.com>,
	"Kaiwen Deng" <kaiwenx.deng@intel.com>,
	"Kiran Kumar K" <kirankumark@marvell.com>,
	"Lunyuan Cui" <lunyuanx.cui@intel.com>,
	"Matan Azrad" <matan@nvidia.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
	"Qi Zhang" <qi.z.zhang@intel.com>,
	"Rahul Lakkireddy" <rahul.lakkireddy@chelsio.com>,
	"Ray Kinsella" <mdr@ashroe.eu>,
	"Satha Rao" <skoteshwar@marvell.com>,
	"Sunil Kumar Kori" <skori@marvell.com>,
	"Thomas Monjalon" <thomas@monjalon.net>,
	"Xiaolong Ye" <xiaolong.ye@intel.com>,
	"Yuying Zhang" <yuying.zhang@intel.com>,
	"Zhichao Zeng" <zhichaox.zeng@intel.com>
Subject: please help backporting some patches to stable release 22.11.6
Date: Tue, 25 Jun 2024 01:04:42 +0100	[thread overview]
Message-ID: <20240625000443.886933-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 2024/07/01.

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

---
ecf408d2aa  Bing Zhao        app/testpmd: fix indirect action flush
b9a87346b0  Chengwen Feng    ethdev: fix strict aliasing in link up
0f9ec0cbd2  Kaiwen Deng      net/iavf: fix VF reset when using DCF
590ee5cd95  Nithin Dabilpuram net/cnxk: update SA userdata and keep original cookie
4c2f14bc6d  Sunil Kumar Kori net/cnxk: fix xstats reset

                 reply	other threads:[~2024-06-25  0:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240625000443.886933-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=aman.deep.singh@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=beilei.xing@intel.com \
    --cc=bingz@nvidia.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dsosnowski@nvidia.com \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=hongbox.li@intel.com \
    --cc=huangdengdui@huawei.com \
    --cc=jerinj@marvell.com \
    --cc=jingjing.wu@intel.com \
    --cc=kaiwenx.deng@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=lunyuanx.cui@intel.com \
    --cc=matan@nvidia.com \
    --cc=mb@smartsharesystems.com \
    --cc=mdr@ashroe.eu \
    --cc=ndabilpuram@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rahul.lakkireddy@chelsio.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xiaolong.ye@intel.com \
    --cc=yuying.zhang@intel.com \
    --cc=zhichaox.zeng@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).