patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Zhou, YidingX" <yidingx.zhou@intel.com>
To: dpdk stable <stable@dpdk.org>,
	"xuemingl@nvidia.com" <xuemingl@nvidia.com>
Cc: Luca Boccassi <bluca@debian.org>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	Akhil Goyal <gakhil@marvell.com>,
	Alejandro Lucero <alejandro.lucero@netronome.com>,
	"Singh, Aman Deep" <aman.deep.singh@intel.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ashish Jain <ashish.jain@nxp.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>,
	Chaoyong He <chaoyong.he@corigine.com>,
	"Xia, Chenbo" <chenbo.xia@intel.com>,
	Chunsong Feng <fengchunsong@huawei.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	David Christensen <david.christensen@broadcom.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	 David Marchand <david.marchand@redhat.com>,
	Duncan Bellamy <dunk@denkimushi.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Gagandeep Singh <g.singh@nxp.com>,
	Hao Chen <chenhao164@huawei.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Huisong Li <lihuisong@huawei.com>,
	Jian Wang <jianwang@trustnetic.com>,
	Jiawen Wu <jiawenwu@trustnetic.com>,
	"Hu, Jiayu" <jiayu.hu@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
	Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
	Lijun Ou <oulijun@huawei.com>,
	Louis Peens <louis.peens@corigine.com>,
	Lunyuan Cui <lunyuanx.cui@intel.com>,
	Matan Azrad <matan@nvidia.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	"Michael Baum" <michaelba@nvidia.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	"Niklas Soderlund" <niklas.soderlund@corigine.com>,
	Nipun Gupta <nipun.gupta@nxp.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	Patrick Fu <patrick.fu@intel.com>,
	"Peng Zhang" <peng.zhang@corigine.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Rolf Neugebauer" <rolf.neugebauer@netronome.com>,
	"Xu, Rosen" <rosen.xu@intel.com>,
	Sachin Saxena <sachin.saxena@oss.nxp.com>,
	"Shreyansh Jain" <shreyansh.jain@nxp.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Stephen Hurd <stephen.hurd@broadcom.com>,
	"Pai G, Sunil" <sunil.pai.g@intel.com>,
	"Zhang, Tianfei" <tianfei.zhang@intel.com>,
	"Tianli Lai" <laitianli@tom.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Walter Heymans <walter.heymans@corigine.com>,
	"Huang, Wei" <wei.huang@intel.com>,
	"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
	"Xiaolong Ye" <xiaolong.ye@intel.com>,
	Xiaoyu Min <jackmin@nvidia.com>,
	"Li, Xiaoyun" <xiaoyun.li@intel.com>,
	Yanglong Wu <yanglong.wu@intel.com>,
	Yisen Zhuang <yisen.zhuang@huawei.com>,
	"Zhang, Yuying" <yuying.zhang@intel.com>
Subject: RE: please help backporting some patches to stable release 20.11.6
Date: Wed, 22 Jun 2022 04:21:10 +0000	[thread overview]
Message-ID: <DM5PR1101MB2107AC82BCBC5E15F3DB526085B29@DM5PR1101MB2107.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220616134733.2042354-1-xuemingl@nvidia.com>


Hi Xueming,

> 676d986b4b  Yiding Zhou      net/iavf: fix crash after VF reset failure

There is no need to backport this to 20.11.6. Thanks.

/Yiding

> -----Original Message-----
> From: Xueming Li <xuemingl@nvidia.com>
> Sent: Thursday, June 16, 2022 9:48 PM
> Cc: xuemingl@nvidia.com; Luca Boccassi <bluca@debian.org>; Ajit Khaparde
> <ajit.khaparde@broadcom.com>; Akhil Goyal <akhil.goyal@nxp.com>; Akhil
> Goyal <gakhil@marvell.com>; Alejandro Lucero
> <alejandro.lucero@netronome.com>; Singh, Aman Deep
> <aman.deep.singh@intel.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; Ashish Jain <ashish.jain@nxp.com>;
> Xing, Beilei <beilei.xing@intel.com>; Iremonger, Bernard
> <bernard.iremonger@intel.com>; Chaoyong He
> <chaoyong.he@corigine.com>; Xia, Chenbo <chenbo.xia@intel.com>;
> Chunsong Feng <fengchunsong@huawei.com>; Dariusz Sosnowski
> <dsosnowski@nvidia.com>; David Christensen
> <david.christensen@broadcom.com>; David Christensen
> <drc@linux.vnet.ibm.com>; David Marchand
> <david.marchand@redhat.com>; Duncan Bellamy <dunk@denkimushi.com>;
> Ferruh Yigit <ferruh.yigit@intel.com>; Gagandeep Singh <g.singh@nxp.com>;
> Hao Chen <chenhao164@huawei.com>; Hemant Agrawal
> <hemant.agrawal@nxp.com>; Huisong Li <lihuisong@huawei.com>; Jian
> Wang <jianwang@trustnetic.com>; Jiawen Wu <jiawenwu@trustnetic.com>;
> Hu, Jiayu <jiayu.hu@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> Kalesh AP <kalesh-anakkur.purayil@broadcom.com>; Konstantin Ananyev
> <konstantin.v.ananyev@yandex.ru>; Lijun Ou <oulijun@huawei.com>; Louis
> Peens <louis.peens@corigine.com>; Lunyuan Cui <lunyuanx.cui@intel.com>;
> Matan Azrad <matan@nvidia.com>; Maxime Coquelin
> <maxime.coquelin@redhat.com>; Michael Baum <michaelba@nvidia.com>;
> Min Hu (Connor) <humin29@huawei.com>; Niklas Soderlund
> <niklas.soderlund@corigine.com>; Nipun Gupta <nipun.gupta@nxp.com>;
> De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Patrick Fu
> <patrick.fu@intel.com>; Peng Zhang <peng.zhang@corigine.com>; Zhang, Qi
> Z <qi.z.zhang@intel.com>; Rolf Neugebauer
> <rolf.neugebauer@netronome.com>; Xu, Rosen <rosen.xu@intel.com>;
> Sachin Saxena <sachin.saxena@oss.nxp.com>; Shreyansh Jain
> <shreyansh.jain@nxp.com>; Somnath Kotur
> <somnath.kotur@broadcom.com>; Stephen Hurd
> <stephen.hurd@broadcom.com>; Pai G, Sunil <sunil.pai.g@intel.com>;
> Zhang, Tianfei <tianfei.zhang@intel.com>; Tianli Lai <laitianli@tom.com>;
> Viacheslav Ovsiienko <viacheslavo@nvidia.com>; Walter Heymans
> <walter.heymans@corigine.com>; Huang, Wei <wei.huang@intel.com>; Wei
> Hu (Xavier) <xavier.huwei@huawei.com>; Xiaolong Ye
> <xiaolong.ye@intel.com>; Xiaoyu Min <jackmin@nvidia.com>; Li, Xiaoyun
> <xiaoyun.li@intel.com>; Yanglong Wu <yanglong.wu@intel.com>; Zhou,
> YidingX <yidingx.zhou@intel.com>; Yisen Zhuang
> <yisen.zhuang@huawei.com>; Zhang, Yuying <yuying.zhang@intel.com>
> Subject: please help backporting some patches to stable release 20.11.6
> 
> 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 06/30/22.
> 
> You can find the a temporary work-in-progress branch of the coming 20.11.6
> release at:
>     https://github.com/steevenlee/dpdk
> 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.
> 
> Xueming Li <xuemingl@nvidia.com>
> 
> ---
> d2fa2632a4  Dariusz Sosnowski net/mlx5: fix RSS hash types adjustment
> 2d47fd3dfb  David Marchand   vhost: fix async access
> 0615dd2aa1  Duncan Bellamy   eal/ppc: fix compilation for musl
> e3d264383b  Gagandeep Singh  crypto/dpaa2_sec: fix crypto operation
> pointer
> e46372d7b0  Huisong Li       app/testpmd: fix port status of bonding slave
> device
> a65342d9d5  Huisong Li       net/hns3: fix MAC and queues HW statistics
> overflow
> 6a925602a9  Jiawen Wu        net/txgbe: fix SGMII mode to link up
> c0278f6e52  Kalesh AP        net/bnxt: fix tunnel stateless offloads
> a213b86821  Michael Baum     net/mlx5: fix LRO validation in Rx setup
> 417be15e5f  Peng Zhang       net/nfp: make sure MTU is never larger than
> mbuf size
> 0b5da8cc52  Tianli Lai       net/dpaa2: fix dpdmux default interface
> ae835aba40  Wei Huang        raw/ifpga: remove virtual devices on close
> 676d986b4b  Yiding Zhou      net/iavf: fix crash after VF reset failure

  parent reply	other threads:[~2022-06-22  4:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220616134733.2042354-1-xuemingl@nvidia.com>
2022-06-17  7:12 ` Jiawen Wu
2022-06-17  8:48   ` Xueming(Steven) Li
2022-06-17 15:20 ` Niklas Soderlund
2022-06-18 12:53   ` Xueming(Steven) Li
2022-06-20  8:29 ` Kalesh Anakkur Purayil
2022-06-20  9:28   ` Xueming(Steven) Li
2022-06-22  4:21 ` Zhou, YidingX [this message]
2022-06-28  3:46 ` Gagandeep Singh
2022-06-28 13:34   ` Xueming(Steven) Li
     [not found] ` <20220720083148.3955227-1-xuemingl@nvidia.com>
2022-07-20 10:32   ` Raslan Darawsheh
2022-07-20 13:18   ` [EXT] " Tomasz Duszynski
2022-07-21 13:27   ` Niklas Söderlund
2022-08-01  5:04   ` Zhou, YidingX
2022-08-11 10:39   ` lihuisong (C)

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=DM5PR1101MB2107AC82BCBC5E15F3DB526085B29@DM5PR1101MB2107.namprd11.prod.outlook.com \
    --to=yidingx.zhou@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=akhil.goyal@nxp.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=aman.deep.singh@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=ashish.jain@nxp.com \
    --cc=beilei.xing@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=bluca@debian.org \
    --cc=chaoyong.he@corigine.com \
    --cc=chenbo.xia@intel.com \
    --cc=chenhao164@huawei.com \
    --cc=david.christensen@broadcom.com \
    --cc=david.marchand@redhat.com \
    --cc=drc@linux.vnet.ibm.com \
    --cc=dsosnowski@nvidia.com \
    --cc=dunk@denkimushi.com \
    --cc=fengchunsong@huawei.com \
    --cc=ferruh.yigit@intel.com \
    --cc=g.singh@nxp.com \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=humin29@huawei.com \
    --cc=jackmin@nvidia.com \
    --cc=jianwang@trustnetic.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=jiayu.hu@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=laitianli@tom.com \
    --cc=lihuisong@huawei.com \
    --cc=louis.peens@corigine.com \
    --cc=lunyuanx.cui@intel.com \
    --cc=matan@nvidia.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=michaelba@nvidia.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=nipun.gupta@nxp.com \
    --cc=oulijun@huawei.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=patrick.fu@intel.com \
    --cc=peng.zhang@corigine.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rolf.neugebauer@netronome.com \
    --cc=rosen.xu@intel.com \
    --cc=sachin.saxena@oss.nxp.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=stephen.hurd@broadcom.com \
    --cc=sunil.pai.g@intel.com \
    --cc=tianfei.zhang@intel.com \
    --cc=viacheslavo@nvidia.com \
    --cc=walter.heymans@corigine.com \
    --cc=wei.huang@intel.com \
    --cc=xavier.huwei@huawei.com \
    --cc=xiaolong.ye@intel.com \
    --cc=xiaoyun.li@intel.com \
    --cc=xuemingl@nvidia.com \
    --cc=yanglong.wu@intel.com \
    --cc=yisen.zhuang@huawei.com \
    --cc=yuying.zhang@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).