From: "lihuisong (C)" <lihuisong@huawei.com>
To: dpdk stable <stable@dpdk.org>, Luca Boccassi <luca.boccassi@gmail.com>
Cc: Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Alexander Kozyrev <akozyrev@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Chengchang Tang <tangchengchang@huawei.com>,
Chengwen Feng <fengchengwen@huawei.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Dongdong Liu <liudongdong3@huawei.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Gage Eads <gage.eads@intel.com>,
Ganapati Kundapura <ganapati.kundapura@intel.com>,
Hongbo Zheng <zhenghongbo3@huawei.com>,
Jerin Jacob <jerinj@marvell.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Lijun Ou <oulijun@huawei.com>, Matan Azrad <matan@nvidia.com>,
Michael Qiu <michael.qiu@intel.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
Neil Horman <nhorman@tuxdriver.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Nikhil Rao <nikhil.rao@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Ray Kinsella <mdr@ashroe.eu>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Shahaf Shuler <shahafs@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Yisen Zhuang <yisen.zhuang@huawei.com>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: please help backporting some patches to stable release 20.11.8
Date: Tue, 21 Mar 2023 17:29:44 +0800 [thread overview]
Message-ID: <c68ad328-0235-499a-34ed-2a3dd5902272@huawei.com> (raw)
In-Reply-To: <20230223094215.3927887-1-luca.boccassi@gmail.com>
Hi Luca Boccassi,
No need to backport the following patches, thanks.
27fd465215 Chengwen Feng net/hns3: declare flow rule keeping capability
52a4e960b4 Huisong Li net/hns3: extract common function to query device
2aec7beaba Huisong Li net/hns3: make getting Tx function static
a8d240786e Huisong Li net/hns3: remove debug condition for Tx prepare
6a934ba4c6 Huisong Li net/hns3: separate Tx prepare from getting Tx function
Best Regards,
Huisong
在 2023/2/23 17:42, luca.boccassi@gmail.com 写道:
> 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 02/03/23.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.8
> release at:
> https://github.com/bluca/dpdk-stable
> 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.
>
> Luca Boccassi
>
> ---
> 1f903ebe2c Alexander Kozyrev net/mlx5: check compressed CQE opcode in vectorized Rx
> 27fd465215 Chengwen Feng net/hns3: declare flow rule keeping capability
> cdede073a5 Ferruh Yigit app/testpmd: fix link check condition on port start
> 04dac73643 Ganapati Kundapura eventdev/crypto: fix enqueue count
> 4b04134cbb Ganapati Kundapura eventdev/crypto: fix failed events
> da73a2a0d1 Ganapati Kundapura eventdev/crypto: fix offset used while flushing events
> f442c04001 Ganapati Kundapura eventdev/crypto: fix overflow in circular buffer
> 52a4e960b4 Huisong Li net/hns3: extract common function to query device
> 10f91af5a5 Huisong Li net/hns3: fix burst mode query with dummy function
> 2aec7beaba Huisong Li net/hns3: make getting Tx function static
> a8d240786e Huisong Li net/hns3: remove debug condition for Tx prepare
> 6a934ba4c6 Huisong Li net/hns3: separate Tx prepare from getting Tx function
> cedb44dc87 Suanming Mou common/mlx5: improve AES-XTS tweak capability check
> 9b31fc9007 Viacheslav Ovsiienko net/mlx5: fix read device clock in real time mode
> .
next prev parent reply other threads:[~2023-03-21 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 9:42 luca.boccassi
2023-03-01 16:15 ` Kundapura, Ganapati
2023-03-02 9:47 ` Luca Boccassi
2023-03-02 10:18 ` Kundapura, Ganapati
2023-03-21 9:29 ` lihuisong (C) [this message]
2023-03-15 22:49 luca.boccassi
2023-03-21 9:37 ` lihuisong (C)
2023-03-22 0:43 luca.boccassi
2023-03-29 1:05 luca.boccassi
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=c68ad328-0235-499a-34ed-2a3dd5902272@huawei.com \
--to=lihuisong@huawei.com \
--cc=abhinandan.gujjar@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=akozyrev@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=drc@linux.vnet.ibm.com \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=gage.eads@intel.com \
--cc=ganapati.kundapura@intel.com \
--cc=humin29@huawei.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=liudongdong3@huawei.com \
--cc=luca.boccassi@gmail.com \
--cc=matan@nvidia.com \
--cc=mdr@ashroe.eu \
--cc=michael.qiu@intel.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=nhorman@tuxdriver.com \
--cc=nikhil.rao@intel.com \
--cc=oulijun@huawei.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=shahafs@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=tangchengchang@huawei.com \
--cc=viacheslavo@nvidia.com \
--cc=wenzhuo.lu@intel.com \
--cc=xavier.huwei@huawei.com \
--cc=yisen.zhuang@huawei.com \
--cc=yskoh@mellanox.com \
--cc=zhenghongbo3@huawei.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).