From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'dpdk stable'" <stable@dpdk.org>
Cc: "'Xueming Li'" <xuemingl@nvidia.com>
Subject: RE: please help backporting some patches to stable release 20.11.6
Date: Fri, 17 Jun 2022 15:12:46 +0800 [thread overview]
Message-ID: <003101d88219$a6e68c70$f4b3a550$@trustnetic.com> (raw)
In-Reply-To: <20220616134733.2042354-1-xuemingl@nvidia.com>
On Thursday, June 16, 2022 9:48 PM, Xueming Li wrote:
> 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 06/30/22.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.6
> release at:
> https://github.com/steevenlee/dpdk
> 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=d90e6ae6f936ecdc2fd3
> 811ff9f26aec7f3c06eb
>
> 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.
>
> Xueming Li <xuemingl@nvidia.com>
>
> ---
> 6a925602a9 Jiawen Wu net/txgbe: fix SGMII mode to link up
I prefer not to backport this patch to 20.11.
It should be fixed after commit f611dada1af8 ("net/txgbe: update link setup
process of backplane NICs"), add backport to 21.11.
next parent reply other threads:[~2022-06-17 7:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220616134733.2042354-1-xuemingl@nvidia.com>
2022-06-17 7:12 ` Jiawen Wu [this message]
2022-06-17 8:48 ` Xueming(Steven) Li
2022-06-17 15:20 ` Niklas Soderlund
2022-06-18 12:53 ` Xueming(Steven) Li
2022-06-20 8:29 ` Kalesh Anakkur Purayil
2022-06-20 9:28 ` Xueming(Steven) Li
2022-06-22 4:21 ` Zhou, YidingX
2022-06-28 3:46 ` Gagandeep Singh
2022-06-28 13:34 ` Xueming(Steven) Li
[not found] ` <20220720083148.3955227-1-xuemingl@nvidia.com>
2022-07-20 10:32 ` Raslan Darawsheh
2022-07-20 13:18 ` [EXT] " Tomasz Duszynski
2022-07-21 13:27 ` Niklas Söderlund
2022-08-01 5:04 ` Zhou, YidingX
2022-08-11 10:39 ` lihuisong (C)
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='003101d88219$a6e68c70$f4b3a550$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--cc=stable@dpdk.org \
--cc=xuemingl@nvidia.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).