From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Subject: [dpdk-stable] please help backporting some patches to stable release 19.11.6
Date: Tue, 17 Nov 2020 11:28:37 +0000 [thread overview]
Message-ID: <20201117112837.1963078-1-luca.boccassi@gmail.com> (raw)
Hi commit authors (and maintainers),
I didn't apply following commits from DPDK main to 19.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 19.11 branch, or
- Indicate that the patch should not be backported
Please do either of the above by 11/24/20.
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 19.11] foo/bar: fix baz
With git format-patch, this can be achieved by appending the parameter:
--subject-prefix='PATCH 19.11'
Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
FYI, branch 19.11 is located at tree:
https://git.dpdk.org/dpdk-stable
Thanks.
Luca Boccassi
---
fe5d0e85b7 Chenxu Di net/i40e: fix flow director flex configuration
992e6df3da Jiawei Wang common/mlx5: free MR resource on device DMA unmap
next reply other threads:[~2020-11-17 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 11:28 luca.boccassi [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-25 9:07 luca.boccassi
2020-11-09 19:05 luca.boccassi
[not found] ` <20201109190556.3481033-1-luca.boccassi@gmail.com>
2020-11-12 9:19 ` Fu, Patrick
2020-11-12 9:38 ` Luca Boccassi
2020-11-23 1:53 ` oulijun
[not found] <20201102194256.1910550-1-luca.boccassi@gmail.com>
2020-11-02 19:43 ` luca.boccassi
2020-11-03 9:06 ` oulijun
2020-11-03 15:04 ` Ruifeng Wang
2020-11-04 8:42 ` Wangxiaoyun (Cloud)
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=20201117112837.1963078-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).