From: Somnath Kotur <somnath.kotur@broadcom.com>
To: dpdk stable <stable@dpdk.org>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Alvin Zhang <alvinx.zhang@intel.com>,
Amit Bernstein <amitbern@amazon.com>,
Beilei Xing <beilei.xing@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Chenmin Sun <chenmin.sun@intel.com>,
David Marchand <david.marchand@redhat.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Harry van Haaren <harry.van.haaren@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Huisong Li <lihuisong@huawei.com>, Ido Segev <idose@amazon.com>,
Igor Chauskin <igorch@amazon.com>, Jeff Guo <jia.guo@intel.com>,
Jiawei Wang <jiaweiw@nvidia.com>,
Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
Lance Richardson <lance.richardson@broadcom.com>,
Lee Daly <lee.daly@intel.com>, Lijun Ou <oulijun@huawei.com>,
Liron Himi <lironh@marvell.com>,
Martin Spinler <spinler@cesnet.cz>,
Matan Azrad <matan@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Michael Baum <michaelba@nvidia.com>,
Michal Krawczyk <mk@semihalf.com>,
Murphy Yang <murphyx.yang@intel.com>,
Olivier Matz <olivier.matz@6wind.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Shiri Kuzin <shirik@nvidia.com>,
Steve Yang <stevex.yang@intel.com>,
Suanming Mou <suanmingm@nvidia.com>,
Tal Shnaiderman <talshn@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Victor Raj <victor.raj@intel.com>,
Xueming Zhang <xuemingx.zhang@intel.com>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.7
Date: Fri, 19 Feb 2021 13:48:29 +0530 [thread overview]
Message-ID: <CAOBf=mvbK4V2+qXOx7D6xvCuprf-kei78Yc+VzRKxfK+HtSNfw@mail.gmail.com> (raw)
In-Reply-To: <20210204115554.2506672-1-christian.ehrhardt@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 4718 bytes --]
On Thu, Feb 4, 2021 at 5:26 PM Christian Ehrhardt
<christian.ehrhardt@canonical.com> wrote:
>
> Hi commit authors (and maintainers),
>
> 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 02/11/21.
>
> You can find the a temporary work-in-progress branch of the coming 19.11.7
> 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>
>
> ---
> 15cfb0bfc4 Alvin Zhang net/ixgbe: fix configuration of max frame size
> 1f949ad90b Amit Bernstein net/ena: fix Tx doorbell statistics
> 47193beea5 Beilei Xing net/i40e: fix flex payload rule conflict
> 7be7dc6dea Bruce Richardson build: force pkg-config for dependency detection
> 820778fad6 Bruce Richardson vhost: fix missing header includes
> c85ebb39db Dmitry Kozlyuk buildtools: fix archive extraction for LLVM 8
> a38eae8efa Dmitry Kozlyuk buildtools: fix archive extraction for Python 3.5
> 65ef14c576 Dmitry Kozlyuk buildtools: fix pmdinfogen with pyelftools < 0.24
> 08dcd18706 Huisong Li app/testpmd: fix queue stats mapping configuration
> ec12dc5a55 Huisong Li net/hns3: fix Rx/Tx errors stats
> 3213d584b6 Huisong Li net/hns3: fix xstats with id and names
> 8a90f3d8d0 Igor Chauskin net/ena: fix Tx SQ free space assessment
> 1d973d8f4c Igor Chauskin net/ena: prevent double doorbell
> 2ce964954b Jiawei Wang app/testpmd: fix packets dump overlapping
> 73d1cc96be Lance Richardson net/bnxt: fix doorbell write ordering
> c86e930165 Lance Richardson net/bnxt: fix fallback mbuf allocation logic
> e750acef45 Lance Richardson net/bnxt: fix outer UDP checksum Rx offload capability
> d5bbd72246 Lance Richardson net/bnxt: make offload flags mapping per-ring
> 48a580c5df Lance Richardson net/bnxt: set correct checksum status in mbuf
> f77b3c3a7b Lijun Ou net/hns3: adjust some comments
> 30d3072070 Liron Himi net/mvpp2: introduce fixup for FIFO overrun
> 8e1630e0f1 Michael Baum net/mlx4: fix device detach
> 4a7f979af2 Michael Baum net/mlx5: remove CQE padding device argument
> 05cffdcfa0 Michal Krawczyk net/ena: validate Rx req ID upon acquiring descriptor
> 75c6287f25 Murphy Yang net/ice: fix outer checksum flags
> de6aede17b Olivier Matz service: propagate init error in EAL
> d5be7f9375 Qi Zhang net/ice/base: update add scheduler node counter
> d362e6f6ac Shiri Kuzin net/mlx5: fix VXLAN decap on non-VXLAN flow
> 9d276b439a Somnath Kotur net/bnxt: fix error handling in device start
> c9ffd6f886 Somnath Kotur net/bnxt: fix lock init and destroy
> 70517a3a8f Somnath Kotur net/bnxt: fix PF resource query
Hi Christian,
I just posted the backported version of
patches 1 and 2 above . The 3rd one ( 70517a3a8f Somnath Kotur
net/bnxt: fix PF resource query)
is not applicable for a backport as it's needs some other changes that
are in 20.08 etc . Please apply the ones i've sent to 19.11.7
Thanks
Som
> 14801aa3fb Steve Yang net/ice: fix jumbo frame flag condition
> 48554c7db7 Steve Yang net/ixgbe: fix jumbo frame flag condition
> 84a22cbcc4 Suanming Mou net/mlx5: fix crash on secondary process port close
> 2b36c30b8c Suanming Mou net/mlx5: fix port attach in secondary process
> 16047bd015 Tal Shnaiderman net/mlx5: fix comparison sign in flow engine
> 45eb6a1dfe Thomas Monjalon lib: fix doxygen for parameters of function pointers
> 81c3b97735 Viacheslav Ovsiienko net/mlx5: fix Verbs memory allocation callback
next prev parent reply other threads:[~2021-02-19 8:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210204115554.2506672-1-christian.ehrhardt@canonical.com>
2021-02-04 13:44 ` [dpdk-stable] [EXT] " Liron Himi
2021-02-04 14:43 ` [dpdk-stable] " Richardson, Bruce
2021-02-04 16:59 ` Maxime Coquelin
2021-02-04 20:16 ` Dmitry Kozlyuk
2021-02-08 16:39 ` Lance Richardson
2021-02-12 8:11 ` Christian Ehrhardt
2021-02-12 9:16 ` Richardson, Bruce
2021-02-12 14:38 ` Slava Ovsiienko
2021-02-19 8:18 ` Somnath Kotur [this message]
[not found] <20210215133002.1856070-1-christian.ehrhardt@canonical.com>
2021-02-19 6:23 ` [dpdk-stable] 回复: " Feifei Wang
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='CAOBf=mvbK4V2+qXOx7D6xvCuprf-kei78Yc+VzRKxfK+HtSNfw@mail.gmail.com' \
--to=somnath.kotur@broadcom.com \
--cc=ajit.khaparde@broadcom.com \
--cc=alvinx.zhang@intel.com \
--cc=amitbern@amazon.com \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenmin.sun@intel.com \
--cc=david.marchand@redhat.com \
--cc=dmitry.kozliuk@gmail.com \
--cc=ferruh.yigit@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=idose@amazon.com \
--cc=igorch@amazon.com \
--cc=jia.guo@intel.com \
--cc=jiaweiw@nvidia.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=lance.richardson@broadcom.com \
--cc=lee.daly@intel.com \
--cc=lihuisong@huawei.com \
--cc=lironh@marvell.com \
--cc=matan@nvidia.com \
--cc=maxime.coquelin@redhat.com \
--cc=michaelba@nvidia.com \
--cc=mk@semihalf.com \
--cc=murphyx.yang@intel.com \
--cc=olivier.matz@6wind.com \
--cc=oulijun@huawei.com \
--cc=qi.z.zhang@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=shirik@nvidia.com \
--cc=spinler@cesnet.cz \
--cc=stable@dpdk.org \
--cc=stevex.yang@intel.com \
--cc=suanmingm@nvidia.com \
--cc=talshn@nvidia.com \
--cc=thomas@monjalon.net \
--cc=venkatkumar.duvvuru@broadcom.com \
--cc=viacheslavo@nvidia.com \
--cc=victor.raj@intel.com \
--cc=xuemingx.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).