From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Lior Margalit <lmargalit@nvidia.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.10
Date: Wed, 11 Aug 2021 13:24:20 +0200 [thread overview]
Message-ID: <CAATJJ0+UeZtiBZVXUOrwCU9kC=T6-WwjkHp2KASyTUpuezEYAw@mail.gmail.com> (raw)
In-Reply-To: <DM6PR12MB4186BDB3EFC5983E3C9BE466CDF89@DM6PR12MB4186.namprd12.prod.outlook.com>
On Wed, Aug 11, 2021 at 12:24 PM Lior Margalit <lmargalit@nvidia.com> wrote:
>
> Hi,
>
> Regarding my patches:
>
> fa06906a48 Lior Margalit net/mlx5: fix IPIP multi-tunnel validation
> -> sent the attached backported patch.
>
> 3e455a97dc Lior Margalit net/mlx5: fix RSS expansion for GTP
> 5e1db76dd8 Lior Margalit net/mlx5: fix RSS flow rule with L4 mismatch
> -> these patches are not relevant for 19.11
Thanks for all three updates!
> Thank you,
> Lior
>
>
> -----Original Message-----
> From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com>
> Sent: Tuesday, August 10, 2021 6:40 PM
> Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>; Akhil Goyal <gakhil@marvell.com>; Aman Deep Singh <aman.deep.singh@intel.com>; Anatoly Burakov <anatoly.burakov@intel.com>; Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>; Arek Kusztal <arkadiuszx.kusztal@intel.com>; Beilei Xing <beilei.xing@intel.com>; Bruce Richardson <bruce.richardson@intel.com>; Chenbo Xia <chenbo.xia@intel.com>; Chengchang Tang <tangchengchang@huawei.com>; Cheng Jiang <cheng1.jiang@intel.com>; Chengwen Feng <fengchengwen@huawei.com>; Christian Ehrhardt <christian.ehrhardt@canonical.com>; Ciara Power <ciara.power@intel.com>; Cristian Dumitrescu <cristian.dumitrescu@intel.com>; Dapeng Yu <dapengx.yu@intel.com>; David Marchand <david.marchand@redhat.com>; Declan Doherty <declan.doherty@intel.com>; Deepak Kumar Jain <deepak.k.jain@intel.com>; Dmitry Kozlyuk <dkozlyuk@nvidia.com>; Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>; Evgeny Schemeilin <evgenys@amazon.com>; Fan Zhang <roy.fan.zhang@intel.com>; Feifei Wang <feifei.wang2@arm.com>; Fiona Trahe <fiona.trahe@intel.com>; Ghalem Boudour <ghalem.boudour@6wind.com>; Gregory Etelson <getelson@nvidia.com>; Hemant Agrawal <hemant.agrawal@nxp.com>; Henry Nadeau <hnadeau@iol.unh.edu>; Hongbo Zheng <zhenghongbo3@huawei.com>; Huisong Li <lihuisong@huawei.com>; Igor Chauskin <igorch@amazon.com>; Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>; Jakub Grajciar <jgrajcia@cisco.com>; Jasvinder Singh <jasvinder.singh@intel.com>; Jay Jayatheerthan <jay.jayatheerthan@intel.com>; Jerin Jacob <jerinj@marvell.com>; Jian Wang <jianwang@trustnetic.com>; Jiawen Wu <jiawenwu@trustnetic.com>; Jingjing Wu <jingjing.wu@intel.com>; John Griffin <john.griffin@intel.com>; John McNamara <john.mcnamara@intel.com>; Kai Ji <kai.ji@intel.com>; Kalesh AP <kalesh-anakkur.purayil@broadcom.com>; Keith Wiles <keith.wiles@intel.com>; Kiran Kumar K <kirankumark@marvell.com>; Konstantin Ananyev <konstantin.ananyev@intel.com>; Lance Richardson <lance.richardson@broadcom.com>; Lijun Ou <oulijun@huawei.com>; Lingli Chen <linglix.chen@intel.com>; Lior Margalit <lmargalit@nvidia.com>; NBU-Contact-longli <longli@microsoft.com>; Luca Boccassi <bluca@debian.org>
> Subject: please help backporting some patches to stable release 19.11.10
>
> External email: Use caution opening links or attachments
>
>
> 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 08/17/21.
>
> You can find the a temporary work-in-progress branch of the coming 19.11.10 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. split in two for mail restrictions :-/
>
> ---
> b3fa83945a Ajit Khaparde net/bnxt: fix ring allocation and free
> 135e3a4046 Arek Kusztal crypto/qat: disable asymmetric crypto on GEN3
> 2fefa0942e Beilei Xing net/i40e: fix flow director input set conflict
> 33d2ee0010 Beilei Xing net/iavf: fix scalar Rx
> 976ddf2f5a Chengchang Tang net/hns3: fix residual MAC address entry
> 2d91b28730 Cheng Jiang net/virtio: fix refill order in packed ring datapath
> 699fa1d40e Chengwen Feng net/hns3: fix Arm SVE build with GCC 8.3
> 9b290a3a63 Chengwen Feng net/hns3: fix flow rule list in multi-process
> 31c5af644b Christian Ehrhardt vfio: add stdbool include
> e391a7b7f8 Dapeng Yu net/i40e: fix multi-process shared data
> 03a91d7efb Dapeng Yu net/ice: fix default RSS key generation
> e9b3d79b06 Dmitry Kozlyuk bus: clarify log for non-NUMA-aware devices
> e8c90926bd Dmitry Kozlyuk doc: fix build on Windows with Meson 0.58
> 1c196da274 Feifei Wang net/mlx5: fix r/w lock usage in DMA unmap
> 3e7008459d Ghalem Boudour net/ena: enable multi-segment in Tx offload flags
> 494d6863c2 Gregory Etelson net/mlx5: fix representor interrupt handler
> 9c30a6f3c9 Henry Nadeau doc: fix spelling
> ee930d38ff Hongbo Zheng net/hns3: fix timing of clearing interrupt source
> c6ccd1e392 Huisong Li sched: rework configuration failure handling
> 4e8169eb0d Ivan Ilchenko net/virtio: fix Rx scatter offload
> 8c98bf791c Jasvinder Singh doc: remove old deprecation notice for sched
> 93d5bdb5e3 Kai Ji crypto/aesni_gcm: fix performance on some AVX512 CPUs
> 70c7d4184c Kalesh AP net/bnxt: fix auto-negociation on Whitney+
> 8ac3cbba62 Kalesh AP net/bnxt: invoke device removal event on recovery failure
> 46c451d905 Kalesh AP net/bnxt: remove unnecessary comment
> 5ed30db87f Lance Richardson net/bnxt: fix missing barriers in completion handling c6c90a33de Lance Richardson net/bnxt: fix ring and context memory allocation 008feb839f Lance Richardson net/bnxt: fix Rx burst size constraint
> fa06906a48 Lior Margalit net/mlx5: fix IPIP multi-tunnel validation
> 3e455a97dc Lior Margalit net/mlx5: fix RSS expansion for GTP
> 5e1db76dd8 Lior Margalit net/mlx5: fix RSS flow rule with L4 mismatch
> 2f6c2adbe5 Michael Baum common/mlx5: fix memory region leak
> b57e105381 Michal Krawczyk net/ena: trigger reset on Tx prepare failure 6922655cad Naga Harish K S V eventdev: fix event port setup in Tx adapter 4e30586dcd Nathan Skrzypczak net/memif: fix abstract socket address length
> cd27047dbe Nick Connolly build: support drivers symlink on Windows
> a46bd97f60 Olivier Matz net/tap: fix Rx checksum flags on IP options packets
> 375474b4d9 Olivier Matz net/tap: fix Rx checksum flags on TCP packets
> ca7204b921 Owen Hilyard tests/cmdline: fix memory leaks
> 45f6a19f65 Qi Zhang net/ice: fix data path in secondary process
> f8b3326f31 Qi Zhang net/ice: fix data path selection in secondary process
> 4ea794318a Rebecca Troy test/crypto: fix autotest function parameters
> d81cea5280 Satheesh Paul net/cnxk: fix default MCAM allocation size
> 03c8f2fe11 Somnath Kotur net/bnxt: detect bad opaque in Rx completion
> 219842b999 Somnath Kotur net/bnxt: workaround spurious zero stats in Thor
> 128c22b998 Stephen Hemminger eal: fix argument in 32-bit safe BSF function
> 920bdbf1bd Steve Yang net/i40e: fix raw packet flow director
> 45633c460c Suanming Mou net/mlx5: workaround drop action with old kernel
> b6b8a1ebd4 Viacheslav Ovsiienko app/testpmd: fix offloads for newly attached port 0fd928bbba Viacheslav Ovsiienko common/mlx5: fix compatibility with OFED port query API
> d0cf77e8c2 Viacheslav Ovsiienko common/mlx5: use new port query API if available ec837ad0fc Viacheslav Ovsiienko net/mlx5: fix multi-segment inline for the first segments
> 9f430dd751 Viacheslav Ovsiienko net/mlx5: fix RoCE LAG bond device probing c150dff40d Viacheslav Ovsiienko net/mlx5: fix Rx queue timestamp format 6b157f3bfa Viacheslav Ovsiienko net/mlx5: fix switchdev mode recognition
> 706ba48665 Xiao Wang vhost: check header for legacy dequeue offload
> 84f4764c22 Xiaoyu Min net/mlx5: fix MPLS RSS expansion
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2021-08-11 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210810153941.749002-1-christian.ehrhardt@canonical.com>
2021-08-11 9:10 ` Dmitry Kozlyuk
2021-08-11 9:51 ` Christian Ehrhardt
2021-08-11 10:24 ` Lior Margalit
2021-08-11 11:24 ` Christian Ehrhardt [this message]
2021-08-13 1:29 ` Huisong Li
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='CAATJJ0+UeZtiBZVXUOrwCU9kC=T6-WwjkHp2KASyTUpuezEYAw@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=lmargalit@nvidia.com \
--cc=stable@dpdk.org \
/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).