From: "Mah, Yock Gen" <yock.gen.mah@intel.com>
To: dpdk stable <stable@dpdk.org>
Cc: "Konstantin Ananyev" <konstantin.ananyev@intel.com>,
"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
"Kumara Parameshwaran" <kumaraparamesh92@gmail.com>,
"Lijun Ou" <oulijun@huawei.com>,
"Lior Margalit" <lmargalit@nvidia.com>,
"Long Li" <longli@microsoft.com>,
"Long Wu" <long.wu@corigine.com>,
"Mao YingMing" <maoyingming@baidu.com>,
"Matan Azrad" <matan@mellanox.com>,
"Matan Azrad" <matan@nvidia.com>,
"mattias.ronnblom" <mattias.ronnblom@ericsson.com>,
"Maxime Coquelin" <maxime.coquelin@redhat.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Rao, Nikhil" <nikhil.rao@intel.com>,
"Niklas Soderlund" <niklas.soderlund@corigine.com>,
"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
"Matz, Olivier" <olivier.matz@6wind.com>,
"Ori Kam" <orika@nvidia.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Stillwell Jr, Paul M" <paul.m.stillwell.jr@intel.com>,
"Pavan Nikhilesh" <pbhagavatula@marvell.com>,
"Peng Zhang" <peng.zhang@corigine.com>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"Raja Zidane" <rzidane@nvidia.com>,
"Remy Horton" <remy.horton@intel.com>,
"Rolf Neugebauer" <rolf.neugebauer@netronome.com>,
"Shahaf Shuler" <shahafs@mellanox.com>,
"Shally Verma" <shally.verma@caviumnetworks.com>,
"Shijith Thotton" <sthotton@marvell.com>,
"Shiqi Liu" <835703180@qq.com>, "Su, Simei" <simei.su@intel.com>,
"Somnath Kotur" <somnath.kotur@broadcom.com>,
"Suanming Mou" <suanmingm@mellanox.com>,
"Sunila Sahu" <sunila.sahu@caviumnetworks.com>,
"Taripin, Samuel" <samuel.taripin@intel.com>,
"Umesh Kartha" <umesh.kartha@caviumnetworks.com>,
"Usman Tanveer" <usman.tanveer@emumba.com>,
"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
"Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>,
"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
"Ling, WeiX" <weix.ling@intel.com>,
"Ma, WenwuX" <wenwux.ma@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Zhou, YidingX" <yidingx.zhou@intel.com>,
"Yisen Zhuang" <yisen.zhuang@huawei.com>,
"Yongseok Koh" <yskoh@mellanox.com>,
"Wang, YuanX" <yuanx.wang@intel.com>
Subject: RE: please help backporting some patches to stable release 19.11.14
Date: Wed, 16 Nov 2022 23:23:33 +0000 [thread overview]
Message-ID: <BY5PR11MB4195D38026CA09FE4954A55DD9079@BY5PR11MB4195.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221111114814.1553136-1-christian.ehrhardt@canonical.com>
> 4841015ffb Mah Yock Gen net/igc: remove unnecessary PHY ID checks
My suggestion is do not backport this patch to 19.11.14 as we never validate the patch on 19.11, it will create unnecessary risk. And, we do not have necessary hardware (i225-IT) with us now for next few weeks to validate it.
-----Original Message-----
From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com>
Sent: Friday, 11 November, 2022 7:48 PM
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>; Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>; Kumara Parameshwaran <kumaraparamesh92@gmail.com>; Lijun Ou <oulijun@huawei.com>; Lior Margalit <lmargalit@nvidia.com>; Long Li <longli@microsoft.com>; Long Wu <long.wu@corigine.com>; Mah, Yock Gen <yock.gen.mah@intel.com>; Mao YingMing <maoyingming@baidu.com>; Matan Azrad <matan@mellanox.com>; Matan Azrad <matan@nvidia.com>; mattias.ronnblom <mattias.ronnblom@ericsson.com>; Maxime Coquelin <maxime.coquelin@redhat.com>; Min Hu (Connor) <humin29@huawei.com>; Morten Brørup <mb@smartsharesystems.com>; Rao, Nikhil <nikhil.rao@intel.com>; Niklas Soderlund <niklas.soderlund@corigine.com>; Nithin Dabilpuram <ndabilpuram@marvell.com>; Matz, Olivier <olivier.matz@6wind.com>; Ori Kam <orika@nvidia.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Stillwell Jr, Paul M <paul.m.stillwell.jr@intel.com>; Pavan Nikhilesh <pbhagavatula@marvell.com>; Peng Zhang <peng.zhang@corigine.com>; Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Nicolau, Radu <radu.nicolau@intel.com>; Raja Zidane <rzidane@nvidia.com>; Remy Horton <remy.horton@intel.com>; Rolf Neugebauer <rolf.neugebauer@netronome.com>; Shahaf Shuler <shahafs@mellanox.com>; Shally Verma <shally.verma@caviumnetworks.com>; Shijith Thotton <sthotton@marvell.com>; Shiqi Liu <835703180@qq.com>; Su, Simei <simei.su@intel.com>; Somnath Kotur <somnath.kotur@broadcom.com>; Suanming Mou <suanmingm@mellanox.com>; Sunila Sahu <sunila.sahu@caviumnetworks.com>; Taripin, Samuel <samuel.taripin@intel.com>; Umesh Kartha <umesh.kartha@caviumnetworks.com>; Usman Tanveer <usman.tanveer@emumba.com>; Viacheslav Ovsiienko <viacheslavo@nvidia.com>; Medvedkin, Vladimir <vladimir.medvedkin@intel.com>; Wei Hu (Xavier) <xavier.huwei@huawei.com>; Ling, WeiX <weix.ling@intel.com>; Ma, WenwuX <wenwux.ma@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>; Zhou, YidingX <yidingx.zhou@intel.com>; Yisen Zhuang <yisen.zhuang@huawei.com>; Yongseok Koh <yskoh@mellanox.com>; Wang, YuanX <yuanx.wang@intel.com>
Subject: please help backporting some patches to stable release 19.11.14
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 11/18/22.
You can find the a temporary work-in-progress branch of the coming 19.11.14 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>
P.S. I had to split the mail again to obey rules of mail providers
---
09b5b2880d Benjamin Le Berre net/bnxt: fix error code during MTU change
830f7e7907 Changpeng Liu vhost: add non-blocking API for posting interrupt
bc6eeb29c6 Chengwen Feng net/hns3: fix VF mailbox message handling
12590fc503 Chengwen Feng net/hns3: optimize SVE Tx performance
e0ec62d6e9 Chengwen Feng net/hns3: revert fix mailbox communication with HW
1a7374c956 Dmitry Kozlyuk eal: fix side effect in some pointer arithmetic macros
329280c53e Erik Gabriel Carrillo service: fix early move to inactive status
8f4ff7de39 Ganapati Kundapura eventdev/crypto: fix multi-process
c05a540902 Huisong Li net/hns3: delete unused markup
b38bd88beb Huisong Li net/hns3: fix clearing hardware MAC statistics
a35799625e Huisong Li net/hns3: fix lock protection of RSS flow rule
904ee370e8 Huisong Li net/hns3: fix packet type for GENEVE
1042ed401f Huisong Li net/hns3: fix restore filter function input
705a508003 Huisong Li net/hns3: fix RSS filter restore
43d8adf389 Huisong Li net/hns3: fix RSS flow rule restore
0d81da2559 Huisong Li net/hns3: fix RSS rule restore
860ed8516a Huisong Li net/hns3: move flow direction rule recovery
df810d1b6e Ivan Malov net/bonding: fix flow flush order on close
9f71a297da Jiawei Wang net/mlx5: fix modify action with tunnel decapsulation
bfa87e21bd Jiawei Wang net/mlx5: fix tunnel header with IPIP offload
b8a55871d5 Jun Qiu gro: trim tail padding bytes
aaa44cb125 Kalesh AP net/bnxt: remove unnecessary check
19ee91c6bd Kevin Liu net/iavf: check illegal packet sizes
72f51b097a Kumara Parameshwaran gro: check payload length after trim
bc5d8fdb70 Long Li net/mlx5: fix Verbs FD leak in secondary process
bb340f56fc Long Wu net/nfp: fix memory leak in Rx
4841015ffb Mah Yock Gen net/igc: remove unnecessary PHY ID checks
4bfb499829 Mao YingMing net/bnxt: fix null pointer dereference in LED config
60b254e392 Matan Azrad net/mlx5: fix Rx queue recovery mechanism
70cb0278a4 Mattias Rönnblom event/dsw: fix flow migration
459531c958 Morten Brørup mempool: fix cache flushing algorithm
a2833ecc5e Morten Brørup mempool: fix get objects from mempool with cache
4edcee19fc Nithin Dabilpuram examples/ipsec-secgw: use Tx checksum offload conditionally
a0a17e2a3e Olivier Matz cryptodev: fix unduly newlines in logs
d5262b521d Olivier Matz mem: fix API doc about allocation on secondary processes
927cb43fe9 Pavan Nikhilesh examples/l3fwd: fix port group mask with AltiVec
dbad6f64f9 Peng Zhang net/nfp: fix internal buffer size and MTU check
b0472e210f Qi Zhang net/ice/base: fix input set of GTPoGRE
c05f2e9688 Radu Nicolau examples/ipsec-secgw: fix Tx checksum offload flag
130bb7da53 Raja Zidane net/mlx5: fix Tx check for hardware descriptor length
d914c01036 Shiqi Liu node: check Rx element allocation
f66323717e Usman Tanveer net/bonding: fix mode 4 with dedicated queues
d15bfd2930 Viacheslav Ovsiienko net/mlx5: fix inline length exceeding descriptor limit
40abb903fe Wenwu Ma examples/vhost: fix use after free
cb5c1b91f7 Yiding Zhou net/iavf: add thread for event callbacks
next prev parent reply other threads:[~2022-11-17 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221111114814.1553136-1-christian.ehrhardt@canonical.com>
2022-11-14 9:57 ` Nicolau, Radu
2022-11-17 8:17 ` 答复: " Mao,Yingming
2022-11-17 8:19 ` Christian Ehrhardt
2022-11-16 10:45 ` Morten Brørup
2022-11-17 6:27 ` Christian Ehrhardt
2022-11-17 7:25 ` Christian Ehrhardt
2022-11-16 23:23 ` Mah, Yock Gen [this message]
2022-11-17 8:49 ` Christian Ehrhardt
2022-11-17 14:33 ` Niklas Soderlund
[not found] <20221116104124.2975325-1-christian.ehrhardt@canonical.com>
2022-11-22 10:57 ` Mattias Rönnblom
2022-11-22 11:35 ` Christian Ehrhardt
[not found] <20221111114803.1553104-1-christian.ehrhardt@canonical.com>
2022-12-01 4:11 ` lihuisong (C)
2022-12-01 6:36 ` Christian Ehrhardt
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=BY5PR11MB4195D38026CA09FE4954A55DD9079@BY5PR11MB4195.namprd11.prod.outlook.com \
--to=yock.gen.mah@intel.com \
--cc=835703180@qq.com \
--cc=humin29@huawei.com \
--cc=konstantin.ananyev@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=kumaraparamesh92@gmail.com \
--cc=lmargalit@nvidia.com \
--cc=long.wu@corigine.com \
--cc=longli@microsoft.com \
--cc=maoyingming@baidu.com \
--cc=matan@mellanox.com \
--cc=matan@nvidia.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=maxime.coquelin@redhat.com \
--cc=mb@smartsharesystems.com \
--cc=ndabilpuram@marvell.com \
--cc=nikhil.rao@intel.com \
--cc=niklas.soderlund@corigine.com \
--cc=olivier.matz@6wind.com \
--cc=orika@nvidia.com \
--cc=oulijun@huawei.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=paul.m.stillwell.jr@intel.com \
--cc=pbhagavatula@marvell.com \
--cc=peng.zhang@corigine.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=radu.nicolau@intel.com \
--cc=remy.horton@intel.com \
--cc=rolf.neugebauer@netronome.com \
--cc=rzidane@nvidia.com \
--cc=samuel.taripin@intel.com \
--cc=shahafs@mellanox.com \
--cc=shally.verma@caviumnetworks.com \
--cc=simei.su@intel.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=sthotton@marvell.com \
--cc=suanmingm@mellanox.com \
--cc=sunila.sahu@caviumnetworks.com \
--cc=umesh.kartha@caviumnetworks.com \
--cc=usman.tanveer@emumba.com \
--cc=viacheslavo@nvidia.com \
--cc=vladimir.medvedkin@intel.com \
--cc=weix.ling@intel.com \
--cc=wenwux.ma@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=xavier.huwei@huawei.com \
--cc=yidingx.zhou@intel.com \
--cc=yisen.zhuang@huawei.com \
--cc=yskoh@mellanox.com \
--cc=yuanx.wang@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).