From: Kevin Traynor <ktraynor@redhat.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dpdk stable <stable@dpdk.org>
Subject: Re: please help backporting some patches to stable release 21.11.7
Date: Wed, 10 Apr 2024 16:52:02 +0100 [thread overview]
Message-ID: <420b045e-32dd-410f-8574-1155e5d96133@redhat.com> (raw)
In-Reply-To: <SJ0PR13MB554597010668F1152386F31C9E002@SJ0PR13MB5545.namprd13.prod.outlook.com>
On 08/04/2024 02:48, Chaoyong He 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 21.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 21.11 branch, or
>> - Indicate that the patch should not be backported
>>
>> Please do either of the above by 04/11/24.
>>
>> You can find the a temporary work-in-progress branch of the coming 21.11.7
>> release at:
>> https://github.com/kevintraynor/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 21.11] foo/bar: fix baz
>>
>> With git format-patch, this can be achieved by appending the parameter:
>> --subject-prefix='PATCH 21.11'
>>
>> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>>
>> FYI, branch 21.11 is located at tree:
>> https://git.dpdk.org/dpdk-stable
>>
>> Thanks.
>>
>> Kevin
>>
>> ---
<snip>
>
>> 8b8f116b19 Chaoyong He net/nfp: fix resource leak for CoreNIC firmware
>> 66d5f53d3e Chaoyong He net/nfp: fix resource leak for exit of CoreNIC
>> firmware
>> a256a1227d Chaoyong He net/nfp: fix resource leak for exit of flower
>> firmware
>> 7c596721ae Chaoyong He net/nfp: fix resource leak for flower firmware
>> a7904d1c6b Chaoyong He net/nfp: fix resource leak for VF
>
> Need not backport, thanks.
>
Thanks Chaoyong, removed from the failed to apply list.
prev parent reply other threads:[~2024-04-10 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 18:10 Kevin Traynor
2024-04-08 1:48 ` Chaoyong He
2024-04-10 15:37 ` Akhil Goyal
2024-04-10 15:50 ` Kevin Traynor
2024-04-10 15:52 ` Kevin Traynor [this message]
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=420b045e-32dd-410f-8574-1155e5d96133@redhat.com \
--to=ktraynor@redhat.com \
--cc=chaoyong.he@corigine.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).