From: "lihuisong (C)" <lihuisong@huawei.com>
To: dpdk stable <stable@dpdk.org>, <luca.boccassi@gmail.com>
Subject: Re: please help backporting some patches to stable release 20.11.7
Date: Tue, 8 Nov 2022 10:00:48 +0800 [thread overview]
Message-ID: <504f25ed-605a-cb16-02d0-8bd4bed31372@huawei.com> (raw)
In-Reply-To: <20221103094037.1103109-1-luca.boccassi@gmail.com>
Hi Luca Boccassi,
It seems that queued patches are not merged into 20.11.7 branch.
These patches in this backporting list are hard to backport.
Is there any other code branch?
Regards,
Huisong
在 2022/11/3 17:40, 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 11/10/22.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.7
> 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
>
> ---
> 8ae946970e Abdullah Ömer Yamaç eal: fix thread name for high order lcores
> 09b5b2880d Benjamin Le Berre net/bnxt: fix error code during MTU change
> b38bd88beb Huisong Li net/hns3: fix clearing hardware MAC statistics
> 0d81da2559 Huisong Li net/hns3: fix RSS rule restore
> 8f81056e5a Qi Zhang net/ice/base: fix 100M speed capability
> 04ab2b2f0b Qi Zhang net/ice/base: fix comment of overloaded GCO bit
> 40ff47dd4b Qi Zhang net/ice/base: fix double VLAN in promiscuous mode
> b0472e210f Qi Zhang net/ice/base: fix input set of GTPoGRE
> 38ef9e1b99 Qi Zhang net/ice/base: fix null pointer dereference
> 27b7bdae1d Qi Zhang net/ice: fix DDP package init
> 3b8c645afa Zhichao Zeng net/iavf: fix outer checksum flags
> 1aaacea174 Zhichao Zeng net/iavf: fix processing VLAN TCI in SSE path
>
> .
next prev parent reply other threads:[~2022-11-08 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 9:40 luca.boccassi
[not found] ` <20221103094132.1103255-1-luca.boccassi@gmail.com>
2022-11-04 18:02 ` Benjamin Le Berre
2022-11-08 2:00 ` lihuisong (C) [this message]
2022-11-08 10:25 ` Luca Boccassi
2022-11-09 2:23 ` lihuisong (C)
2022-11-05 17:26 luca.boccassi
2022-11-17 23:16 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=504f25ed-605a-cb16-02d0-8bd4bed31372@huawei.com \
--to=lihuisong@huawei.com \
--cc=luca.boccassi@gmail.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).