From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Ali Alnubani <alialnu@nvidia.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
Ashish Gupta <ashish.gupta@marvell.com>,
Beilei Xing <beilei.xing@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Ciara Power <ciara.power@intel.com>,
Deepak Kumar Jain <deepak.k.jain@intel.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Jian Wang <jianwang@trustnetic.com>,
Jiawen Wu <jiawenwu@trustnetic.com>, Jie Hai <haijie1@huawei.com>,
John Griffin <john.griffin@intel.com>,
Song Jiale <songx.jiale@intel.com>,
Vikash Poddar <vikash.chandrax.poddar@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: please help backporting some patches to stable release 20.11.9
Date: Fri, 14 Jul 2023 23:51:11 +0100 [thread overview]
Message-ID: <20230714225111.1095683-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 2023/07/21.
You can find the a temporary work-in-progress branch of the coming 20.11.9
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
---
8b4618a7b4 Ciara Power crypto/qat: fix null algorithm digest placement
d7d802daf8 Ferruh Yigit app/testpmd: revert primary process polling all queues fix
5e170dd8b6 Jiawen Wu net/txgbe: fix blocking system events
7cb939f648 Vikash Poddar common/qat: detach crypto from compress build
next reply other threads:[~2023-07-14 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 22:51 luca.boccassi [this message]
2023-07-20 8:31 ` Jiawen Wu
-- strict thread matches above, loose matches on Subject: below --
2023-07-20 11:01 luca.boccassi
2023-06-28 14:12 luca.boccassi
2023-06-29 3:02 ` Jiawen Wu
2023-06-15 1:38 luca.boccassi
2023-06-15 5:49 ` Rongwei Liu
2023-06-15 13:27 ` huangdengdui
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=20230714225111.1095683-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=alialnu@nvidia.com \
--cc=anatoly.burakov@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ashish.gupta@marvell.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=ferruh.yigit@amd.com \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=haijie1@huawei.com \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=john.griffin@intel.com \
--cc=songx.jiale@intel.com \
--cc=stable@dpdk.org \
--cc=vikash.chandrax.poddar@intel.com \
--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).