patches for DPDK stable branches
 help / color / mirror / Atom feed
* RE: please help backporting some patches to stable release 19.11.12
       [not found] <20220309111111.1299669-1-christian.ehrhardt@canonical.com>
@ 2022-03-10 16:22 ` De Lara Guarch, Pablo
  2022-03-11 11:02 ` Dariusz Sosnowski
  1 sibling, 0 replies; 3+ messages in thread
From: De Lara Guarch, Pablo @ 2022-03-10 16:22 UTC (permalink / raw)
  To: dpdk stable
  Cc: Adrien Mazarguil, Ajit Khaparde, Singh, Aman Deep, Anand Rawat,
	Burakov, Anatoly, agh, Andrew Rybchenko, Pei, Andy, Xing, Beilei,
	Dooley, Brian, Richardson, Bruce, Marohn, Byron, Xia, Chenbo,
	Chen Jing D(Mark),
	Maciocco, Christian, Loftus, Ciara, Dumitrescu, Cristian, Yu,
	DapengX, Dariusz Sosnowski, David Harton, David Marchand,
	Dawid Gorecki, Jain, Deepak K, Dmitry Kozlyuk, Evgeny Schemeilin,
	Zhang, Roy Fan, Yigit, Ferruh, Trahe, Fiona, Gavin Hu,
	Gregory Etelson, Harini Ramakrishnan, Harold Huang, Zhang, Helin,
	Hemant Agrawal, Igor Chauskin, Jan Blunck, Singh, Jasvinder,
	Jay Zhou, Jerin Jacob, Jiawei Wang, Liu, Jijiang, Wu, Jingjing,
	Joyce Kong, Karl Bonde Torp, Laatz, Kevin, Liu, KevinX, Ananyev,
	Konstantin, Daly, Lee, Rong, Leyi, Wang, Liang-min, Liron Himi,
	Marcin Wojtas, Matan Azrad, Maxime Coquelin, Ajmera, Megha,
	Michael Baum, Michal Krawczyk, Morten Brorup, Neil Horman,
	Nelio Laranjeiro, Olivier Matz, Ori Kam, Kadam, Pallavi,
	Patrick Fu, Zhang, Peng1X, Phil Yang, Yang, Qiming, Zhang, Qi Z,
	Raja Zidane, Raslan Darawsheh, Ray Kinsella, Remy Horton, Xu,
	Rosen, Edupuganti, Saikrishna, Sergio Gonzalez Monroy,
	Shahaf Shuler, Shai Brandes, Shally Verma, Stephen Hemminger,
	Yang, SteveX, Sunil Kumar Kori, Thomas Monjalon, Zhang, Tianfei,
	Xu, Ting, Tomasz Jozwiak, Tyler Retzlaff, Viacheslav Ovsiienko,
	Vincent Jardin, Huang, Wei, Ma, WenwuX, Lu, Wenzhuo, Wisam Jaddo,
	Xiaolong Ye, Li, Xiaoyun, Ding, Xuan, Wang, Yipeng1,
	Yongseok Koh, Yuanhan Liu, Zhang, Yuying

Hi Christian,

> -----Original Message-----
> From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com>
> Sent: Wednesday, March 9, 2022 11:11 AM
> Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>; Ajit Khaparde
> <ajit.khaparde@broadcom.com>; Singh, Aman Deep
> <aman.deep.singh@intel.com>; Anand Rawat <anand.rawat@intel.com>;
> Burakov, Anatoly <anatoly.burakov@intel.com>; agh <agh@cisco.com>;
> Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>; Pei, Andy
> <andy.pei@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Dooley, Brian
> <brian.dooley@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>;
> Marohn, Byron <byron.marohn@intel.com>; Xia, Chenbo
> <chenbo.xia@intel.com>; Chen Jing D(Mark) <jing.d.chen@intel.com>;
> Maciocco, Christian <christian.maciocco@intel.com>; Loftus, Ciara
> <ciara.loftus@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>; Yu, DapengX <dapengx.yu@intel.com>;
> Dariusz Sosnowski <dsosnowski@nvidia.com>; David Harton
> <dharton@cisco.com>; David Marchand <david.marchand@redhat.com>;
> Dawid Gorecki <dgr@semihalf.com>; Jain, Deepak K
> <deepak.k.jain@intel.com>; Dmitry Kozlyuk <dkozlyuk@nvidia.com>; Evgeny
> Schemeilin <evgenys@amazon.com>; Zhang, Roy Fan
> <roy.fan.zhang@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; Trahe,
> Fiona <fiona.trahe@intel.com>; Gavin Hu <gavin.hu@arm.com>; Gregory
> Etelson <getelson@nvidia.com>; Harini Ramakrishnan
> <harini.ramakrishnan@microsoft.com>; Harold Huang
> <baymaxhuang@gmail.com>; Zhang, Helin <helin.zhang@intel.com>; Hemant
> Agrawal <hemant.agrawal@nxp.com>; Igor Chauskin <igorch@amazon.com>;
> Jan Blunck <jblunck@infradead.org>; Singh, Jasvinder
> <jasvinder.singh@intel.com>; Jay Zhou <jianjay.zhou@huawei.com>; Jerin Jacob
> <jerinj@marvell.com>; Jiawei Wang <jiaweiw@nvidia.com>; Liu, Jijiang
> <jijiang.liu@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>; Joyce Kong
> <joyce.kong@arm.com>; Karl Bonde Torp <k.torp@samsung.com>; Laatz, Kevin
> <kevin.laatz@intel.com>; Liu, KevinX <kevinx.liu@intel.com>; Ananyev,
> Konstantin <konstantin.ananyev@intel.com>; Daly, Lee <lee.daly@intel.com>;
> Rong, Leyi <leyi.rong@intel.com>; Wang, Liang-min <liang-
> min.wang@intel.com>; Liron Himi <lironh@marvell.com>; Marcin Wojtas
> <mw@semihalf.com>; Matan Azrad <matan@nvidia.com>; Maxime Coquelin
> <maxime.coquelin@redhat.com>; Ajmera, Megha <megha.ajmera@intel.com>;
> Michael Baum <michaelba@nvidia.com>; Michal Krawczyk
> <mk@semihalf.com>; Morten Brorup <mb@smartsharesystems.com>; Neil
> Horman <nhorman@tuxdriver.com>; Nelio Laranjeiro
> <nelio.laranjeiro@6wind.com>; Olivier Matz <olivier.matz@6wind.com>; Ori
> Kam <orika@nvidia.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Kadam, Pallavi <pallavi.kadam@intel.com>;
> Patrick Fu <patrick.fu@intel.com>; Zhang, Peng1X <peng1x.zhang@intel.com>;
> Phil Yang <phil.yang@arm.com>; Yang, Qiming <qiming.yang@intel.com>;
> Zhang, Qi Z <qi.z.zhang@intel.com>; Raja Zidane <rzidane@nvidia.com>; Raslan
> Darawsheh <rasland@nvidia.com>; Ray Kinsella <mdr@ashroe.eu>; Remy
> Horton <remy.horton@intel.com>; Xu, Rosen <rosen.xu@intel.com>;
> Edupuganti, Saikrishna <saikrishna.edupuganti@intel.com>; Sergio Gonzalez
> Monroy <sergio.gonzalez.monroy@intel.com>; Shahaf Shuler
> <shahafs@mellanox.com>; Shai Brandes <shaibran@amazon.com>; Shally
> Verma <shally.verma@caviumnetworks.com>; Stephen Hemminger
> <stephen@networkplumber.org>; Yang, SteveX <stevex.yang@intel.com>; Sunil
> Kumar Kori <skori@marvell.com>; Thomas Monjalon <thomas@monjalon.net>;
> Zhang, Tianfei <tianfei.zhang@intel.com>; Xu, Ting <ting.xu@intel.com>;
> Tomasz Jozwiak <tomaszx.jozwiak@intel.com>; Tyler Retzlaff
> <roretzla@linux.microsoft.com>; Viacheslav Ovsiienko
> <viacheslavo@nvidia.com>; Vincent Jardin <vincent.jardin@6wind.com>;
> Huang, Wei <wei.huang@intel.com>; Ma, WenwuX <wenwux.ma@intel.com>;
> Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wisam Jaddo <wisamm@nvidia.com>;
> Xiaolong Ye <xiaolong.ye@intel.com>; Li, Xiaoyun <xiaoyun.li@intel.com>;
> Ding, Xuan <xuan.ding@intel.com>; Wang, Yipeng1
> <yipeng1.wang@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Yuanhan
> Liu <yuanhan.liu@linux.intel.com>; Zhang, Yuying <yuying.zhang@intel.com>
> Subject: please help backporting some patches to stable release 19.11.12
> 
> 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 19.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 19.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 03/18/22.
> 
> You can find the a temporary work-in-progress branch of the coming 19.11.12
> release at:
>     https://github.com/cpaelzer/dpdk-stable-queue
> 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 19.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 19.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 19.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
> 
> ---
> d7e9c02cca  Brian Dooley     eal: add missing C++ guards
> dbf9fc1dac  Brian Dooley     ethdev: add missing C++ guards
> cedca4084a  Brian Dooley     vhost: add missing C++ guards
> b26431a617  Ciara Loftus     net/af_xdp: ensure socket is deleted on Rx queue
> setup error
> a4ba773679  Dapeng Yu        net/i40e: enable maximum frame size at port level
> 98008ce6ec  Dariusz Sosnowski net/mlx5: fix MPLS/GRE Verbs spec ordering
> 9ae7a13f82  Dawid Gorecki    net/ena: check memory BAR before initializing LLQ
> 2bae75eaa2  Dawid Gorecki    net/ena: fix reset reason being overwritten
> be66461cba  Dmitry Kozlyuk   common/mlx5: add Netlink event helpers
> 655c3c26c1  Dmitry Kozlyuk   net/mlx5: fix initial link status detection
> 17f95513ad  Dmitry Kozlyuk   net/mlx5: fix link status change detection
> dcd398f946  Harold Huang     net/kni: fix config initialization
> 6d4f1066be  Jiawei Wang      net/mlx5: fix NIC egress flow mismatch in
> switchdev mode
> 4bab7ea60c  Karl Bonde Torp  build: fix build on FreeBSD with Meson 0.61.1
> d852fec1be  Kevin Liu        net/ice: fix Tx offload path choice
> 9c9fad3dfa  Megha Ajmera     examples/qos_sched: fix core mask overflow
> 67e1bb42b9  Michael Baum     doc: correct name of BlueField-2 in mlx5 guide
> dcbaafdc8f  Michael Baum     net/mlx5: fix sibling device config check
> 96d0dc2a3c  Pablo de Lara    crypto/ipsec_mb: fix ZUC operation overwrite
> ecda2c40ac  Pablo de Lara    efd: fix uninitialized structure

I submitted a patch to backport the last commit (ecda2c40ac).
Commit 96d0dc2a3c  does not need to be backported.

Thanks,
Pablo

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: please help backporting some patches to stable release 19.11.12
       [not found] <20220309111111.1299669-1-christian.ehrhardt@canonical.com>
  2022-03-10 16:22 ` please help backporting some patches to stable release 19.11.12 De Lara Guarch, Pablo
@ 2022-03-11 11:02 ` Dariusz Sosnowski
  1 sibling, 0 replies; 3+ messages in thread
From: Dariusz Sosnowski @ 2022-03-11 11:02 UTC (permalink / raw)
  To: christian.ehrhardt; +Cc: dpdk stable

Hi Christian

> 98008ce6ec  Dariusz Sosnowski net/mlx5: fix MPLS/GRE Verbs spec ordering

This patch does not have to be backported.

Best regards,
Dariusz Sosnowski

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: please help backporting some patches to stable release 19.11.12
       [not found] <20220317141727.1954868-1-christian.ehrhardt@canonical.com>
@ 2022-03-21  9:08 ` Richardson, Bruce
  0 siblings, 0 replies; 3+ messages in thread
From: Richardson, Bruce @ 2022-03-21  9:08 UTC (permalink / raw)
  To: dpdk stable


> -----Original Message-----
> From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com>
> Sent: Thursday, March 17, 2022 2:17 PM
> Cc: Singh, Aman Deep <aman.deep.singh@intel.com>; Iremonger, Bernard
> <bernard.iremonger@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>;
> Gregory Etelson <getelson@nvidia.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Mcnamara, John <john.mcnamara@intel.com>;
> Kovacevic, Marko <marko.kovacevic@intel.com>; Xu, Ting
> <ting.xu@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Subject: please help backporting some patches to stable release 19.11.12
> 
> 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 19.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 19.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 03/20/22.
> 
> You can find the a temporary work-in-progress branch of the coming
> 19.11.12
> release at:
>     https://github.com/cpaelzer/dpdk-stable-queue
> 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 19.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 19.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 19.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
> 
> ---
> c265d58619  Bruce Richardson doc: replace characters for (R) symbol in
> Linux guide
> a058de216c  Gregory Etelson  app/testpmd: fix GTP header parsing in
> checksum engine

Hi,

I am not sure that my doc fix is worth backporting. If I get the chance I will do a new version of it, but if it is not backported no serious issues will occur as the docs seem fine without it. It's more a convenience for developers.

/Bruce

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-03-21  9:08 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20220309111111.1299669-1-christian.ehrhardt@canonical.com>
2022-03-10 16:22 ` please help backporting some patches to stable release 19.11.12 De Lara Guarch, Pablo
2022-03-11 11:02 ` Dariusz Sosnowski
     [not found] <20220317141727.1954868-1-christian.ehrhardt@canonical.com>
2022-03-21  9:08 ` Richardson, Bruce

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).