From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Itamar Gozlan <igozlan@nvidia.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Kumara Parameshwaran <kumaraparamesh92@gmail.com>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Gregory Etelson <getelson@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: please help backporting some patches to stable release 22.11.5
Date: Thu, 28 Mar 2024 17:27:45 +0000 [thread overview]
Message-ID: <20240328172745.3879385-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 22.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 22.11 branch, or
- Indicate that the patch should not be backported
Please do either of the above by 2024/04/03.
You can find the a temporary work-in-progress branch of the coming 22.11.5
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 22.11] foo/bar: fix baz
With git format-patch, this can be achieved by appending the parameter:
--subject-prefix='PATCH 22.11'
Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
FYI, branch 22.11 is located at tree:
https://git.dpdk.org/dpdk-stable
Thanks.
Luca Boccassi
---
df33fb53e4 Honnappa Nagarahalli rcu: fix acked token in debug log
063cddfc74 Honnappa Nagarahalli rcu: use atomic operation on acked token
547f294357 Kumara Parameshwaran gro: fix reordering of packets
323b626a86 Stephen Hemminger net/sfc: fix compile-time check
e23edbc509 Itamar Gozlan net/mlx5/hws: skip item when inserting rules by index
3232c95d2c Nithin Dabilpuram net/cnxk: fix indirect mbuf handling in Tx
5ecc8df4fa Dariusz Sosnowski net/mlx5: fix async flow create error handling
ff9433b578 Dariusz Sosnowski net/mlx5: fix flow configure validation
727283742a Dariusz Sosnowski net/mlx5: fix rollback on failed flow configure
4359d9d1f7 Gregory Etelson net/mlx5: fix sync meter processing in HWS
dc7faa1351 Gregory Etelson net/mlx5: fix sync flow meter action
next reply other threads:[~2024-03-28 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 17:27 luca.boccassi [this message]
2024-03-28 17:31 ` Gregory Etelson
-- strict thread matches above, loose matches on Subject: below --
2024-03-25 12:18 luca.boccassi
2024-03-18 15:41 luca.boccassi
2024-03-14 0:17 luca.boccassi
2024-03-07 1:38 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=20240328172745.3879385-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=dsosnowski@nvidia.com \
--cc=getelson@nvidia.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=igozlan@nvidia.com \
--cc=kumaraparamesh92@gmail.com \
--cc=ndabilpuram@marvell.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).