From: Kevin Traynor <ktraynor@redhat.com>
To: dpdk stable <stable@dpdk.org>
Cc: Chenbo Xia <chenbo.xia@intel.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
Jerin Jacob <jerinj@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Satheesh Paul <psatheesh@marvell.com>,
Shijith Thotton <sthotton@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Xuan Ding <xuan.ding@intel.com>, Yuan Wang <yuanx.wang@intel.com>
Subject: please help backporting some patches to stable release 21.11.1
Date: Tue, 1 Mar 2022 11:21:51 +0000 [thread overview]
Message-ID: <20220301112151.338828-1-ktraynor@redhat.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 21.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 21.11 branch, or
- Indicate that the patch should not be backported
Please do either of the above by 03/07/22.
You can find the a temporary work-in-progress branch of the coming 21.11.1
release at:
https://github.com/kevintraynor/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 21.11] foo/bar: fix baz
With git format-patch, this can be achieved by appending the parameter:
--subject-prefix='PATCH 21.11'
Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
FYI, branch 21.11 is located at tree:
https://git.dpdk.org/dpdk-stable
Thanks.
Kevin
---
315d14d705 Gowrishankar Muthukrishnan event/cnxk: fix memory leaks
3cebc8f35f Satheesh Paul net/cnxk: fix Rx/Tx function update
52ade97e36 Xuan Ding vhost: fix physical address mapping
next reply other threads:[~2022-03-01 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 11:21 Kevin Traynor [this message]
2022-03-08 14:51 ` Kevin Traynor
2022-03-10 13:22 ` David Marchand
2022-03-10 13:27 ` Kevin Traynor
2022-03-10 13:35 ` [EXT] " Gowrishankar Muthukrishnan
2022-03-10 13:23 Kevin Traynor
2022-03-21 16:02 Kevin Traynor
2022-04-05 15:06 Kevin Traynor
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=20220301112151.338828-1-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=gmuthukrishn@marvell.com \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=stable@dpdk.org \
--cc=sthotton@marvell.com \
--cc=xuan.ding@intel.com \
--cc=yuanx.wang@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).