From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Subject: [dpdk-stable] please help backporting some patches to stable release 20.11.3
Date: Mon, 26 Jul 2021 15:41:45 +0100 [thread overview]
Message-ID: <20210726144145.243986-1-luca.boccassi@gmail.com> (raw)
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 08/02/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
---
a1fcde8c80 Michael Baum regex/mlx5: fix leak on device removal
29ca3215f3 Michael Baum regex/mlx5: fix memory region unregistration
d81cea5280 Satheesh Paul net/cnxk: fix default MCAM allocation size
0a37b22875 Wenjun Wu net/ice/base: revert change of first profile mask
next reply other threads:[~2021-07-26 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 14:41 luca.boccassi [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-15 15:04 luca.boccassi
2021-07-16 6:33 ` Somnath Kotur
[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
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=20210726144145.243986-1-luca.boccassi@gmail.com \
--to=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).