From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Beilei Xing <beilei.xing@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Michael Baum <michaelba@nvidia.com>, Ori Kam <orika@nvidia.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: please help backporting some patches to stable release 20.11.8
Date: Wed, 29 Mar 2023 02:05:48 +0100 [thread overview]
Message-ID: <20230329010548.564029-1-luca.boccassi@gmail.com> (raw)
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 31/03/23.
You can find the a temporary work-in-progress branch of the coming 20.11.8
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
---
7bdf7a13ae Michael Baum app/testpmd: fix encap/decap size calculation
next reply other threads:[~2023-03-29 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 1:05 luca.boccassi [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-22 0:43 luca.boccassi
2023-03-15 22:49 luca.boccassi
2023-03-21 9:37 ` lihuisong (C)
2023-02-23 9:42 luca.boccassi
2023-03-01 16:15 ` Kundapura, Ganapati
2023-03-02 9:47 ` Luca Boccassi
2023-03-02 10:18 ` Kundapura, Ganapati
2023-03-21 9:29 ` 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=20230329010548.564029-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=ferruh.yigit@amd.com \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.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).