From: Somnath Kotur <somnath.kotur@broadcom.com>
To: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 20.11.3
Date: Fri, 16 Jul 2021 12:03:44 +0530 [thread overview]
Message-ID: <CAOBf=mtxvw7P_Zr=m_9PemNJ5g0UUpbhfXStX+5Qaw8+7TMKCA@mail.gmail.com> (raw)
In-Reply-To: <20210715150433.2731791-1-luca.boccassi@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]
On Thu, Jul 15, 2021 at 8:34 PM <luca.boccassi@gmail.com> wrote:
>
> Hi commit authors (and maintainers),
>
> 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 07/22/21.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.3
> 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
>
> ---
> b3fa83945a Ajit Khaparde net/bnxt: fix ring allocation and free
> a57d92d73d Cristian Dumitrescu pipeline: fix table entry read
> cfdaa678b3 Dmitry Kozlyuk eal/windows: cleanup interrupt resources
> 3888f31950 Dmitry Kozlyuk eal/windows: fix interrupt thread handle leakage
> 35dff5d3b7 Dmitry Kozlyuk eal/windows: fix interrupt thread ID
> 29343b9030 Richael Zhuang test/power: fix CPU frequency when turbo enabled
> 03c8f2fe11 Somnath Kotur net/bnxt: detect bad opaque in Rx completion
Just FYI i have backported this patch and sent it out to stable just now Luca
> c150dff40d Viacheslav Ovsiienko net/mlx5: fix Rx queue timestamp format
next prev parent reply other threads:[~2021-07-16 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 15:04 luca.boccassi
[not found] ` <20210715150520.2731947-1-luca.boccassi@gmail.com>
2021-07-16 6:12 ` Richael Zhuang
2021-07-16 9:50 ` Luca Boccassi
2021-07-20 15:26 ` Slava Ovsiienko
2021-07-21 12:10 ` Luca Boccassi
2021-07-16 6:33 ` Somnath Kotur [this message]
2021-07-26 14:41 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='CAOBf=mtxvw7P_Zr=m_9PemNJ5g0UUpbhfXStX+5Qaw8+7TMKCA@mail.gmail.com' \
--to=somnath.kotur@broadcom.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).