patches for DPDK stable branches
 help / color / mirror / Atom feed
From: huangdengdui <huangdengdui@huawei.com>
To: dpdk stable <stable@dpdk.org>, <luca.boccassi@gmail.com>
Cc: "Aaron Conole" <aconole@redhat.com>,
	"Alejandro Lucero" <alejandro.lucero@netronome.com>,
	"Anatoly Burakov" <anatoly.burakov@intel.com>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
	"Beilei Xing" <beilei.xing@intel.com>,
	"Bernard Iremonger" <bernard.iremonger@intel.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	"Chaoyong He" <chaoyong.he@corigine.com>,
	"Chengchang Tang" <tangchengchang@huawei.com>,
	"Chengwen Feng" <fengchengwen@huawei.com>,
	"Ciara Power" <ciara.power@intel.com>,
	"Dariusz Sosnowski" <dsosnowski@nvidia.com>,
	"David Marchand" <david.marchand@redhat.com>,
	"Declan Doherty" <declan.doherty@intel.com>,
	"Dongdong Liu" <liudongdong3@huawei.com>,
	"Ferruh Yigit" <ferruh.yigit@amd.com>,
	"Ferruh Yigit" <ferruh.yigit@intel.com>,
	"Heinrich Kuhn" <heinrich.kuhn@netronome.com>,
	"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
	"Ilyes Ben Hamouda" <ilyes.ben_hamouda@6wind.com>,
	"Jiawei Wang" <jiaweiw@nvidia.com>,
	"Jie Hai" <haijie1@huawei.com>, "Kai Ji" <kai.ji@intel.com>,
	"Kiran Kumar K" <kirankumark@marvell.com>,
	"Lijun Ou" <oulijun@huawei.com>, "Matan Azrad" <matan@nvidia.com>,
	"Michael Santana" <maicolgabriel@hotmail.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Niklas Söderlund" <niklas.soderlund@corigine.com>,
	"Olivier Matz" <olivier.matz@6wind.com>,
	"Ori Kam" <orika@nvidia.com>, "Rongwei Liu" <rongweil@nvidia.com>,
	"Saoirse O'Donovan" <saoirse.odonovan@intel.com>,
	"Shahaf Shuler" <shahafs@nvidia.com>,
	"Suanming Mou" <suanmingm@nvidia.com>,
	"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
	"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
	"Wenzhuo Lu" <wenzhuo.lu@intel.com>,
	"Yisen Zhuang" <yisen.zhuang@huawei.com>
Subject: Re: please help backporting some patches to stable release 20.11.9
Date: Thu, 15 Jun 2023 21:27:12 +0800	[thread overview]
Message-ID: <542162e0-1f66-0828-3a86-cad65108f0d5@huawei.com> (raw)
In-Reply-To: <20230615013820.1440549-1-luca.boccassi@gmail.com>

db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue

no need to backport this patch, because it depend on multiple other patches,
in addition, this bug has little impact.

On 2023/6/15 9:38, luca.boccassi@gmail.com wrote:
> 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 20.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 20.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 2023/06/23.
> 
> You can find the a temporary work-in-progress branch of the coming 20.11.9
> 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 20.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 20.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 20.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> e97738919c  Chaoyong He      net/nfp: fix Tx descriptor free logic of NFD3
> c1f0cdae14  Dariusz Sosnowski net/mlx5: fix drop action attribute validation
> db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue
> 0622428215  Jie Hai          net/hns3: fix missing FEC capability
> cd41a27154  Jie Hai          net/hns3: get FEC capability from firmware
> ad4d51d277  Rongwei Liu      net/mlx5: forbid duplicated tag index in pattern template
> 7ae50175c7  Saoirse O'Donovan test/crypto: fix return value for SNOW3G

  parent reply	other threads:[~2023-06-15 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  1:38 luca.boccassi
2023-06-15  5:49 ` Rongwei Liu
2023-06-15 13:27 ` huangdengdui [this message]
2023-06-28 14:12 luca.boccassi
2023-06-29  3:02 ` Jiawen Wu
2023-07-14 22:51 luca.boccassi
2023-07-20  8:31 ` Jiawen Wu
2023-07-20 11:01 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=542162e0-1f66-0828-3a86-cad65108f0d5@huawei.com \
    --to=huangdengdui@huawei.com \
    --cc=aconole@redhat.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=beilei.xing@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chaoyong.he@corigine.com \
    --cc=ciara.power@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=declan.doherty@intel.com \
    --cc=dsosnowski@nvidia.com \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=ferruh.yigit@intel.com \
    --cc=haijie1@huawei.com \
    --cc=heinrich.kuhn@netronome.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=humin29@huawei.com \
    --cc=ilyes.ben_hamouda@6wind.com \
    --cc=jiaweiw@nvidia.com \
    --cc=kai.ji@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=liudongdong3@huawei.com \
    --cc=luca.boccassi@gmail.com \
    --cc=maicolgabriel@hotmail.com \
    --cc=matan@nvidia.com \
    --cc=mb@smartsharesystems.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=olivier.matz@6wind.com \
    --cc=orika@nvidia.com \
    --cc=oulijun@huawei.com \
    --cc=rongweil@nvidia.com \
    --cc=saoirse.odonovan@intel.com \
    --cc=shahafs@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.com \
    --cc=tangchengchang@huawei.com \
    --cc=viacheslavo@nvidia.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=xavier.huwei@huawei.com \
    --cc=yisen.zhuang@huawei.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).