From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Subject: [dpdk-stable] please help backporting some patches to stable release 19.11.1
Date: Thu, 27 Feb 2020 10:07:02 +0000 [thread overview]
Message-ID: <20200227100702.685-1-luca.boccassi@gmail.com> (raw)
Hi commit authors (and maintainers),
I didn't apply following commits from DPDK master 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 March the 5th 2020.
Some notes on stable backports:
A backport should contain a reference to the DPDK master branch commit
in it's commit message in the following fashion:
[ upstream commit <commit's dpdk master 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
---
74f96ffdc1 Kalesh AP net/bnxt: fix return code handling in VLAN config
90c957ef3b Kalesh AP net/bnxt: remove a redundant variable
06387be8ea Matan Azrad net/mlx5: fix encap/decap validation
bc42413bb9 Suanming Mou net/mlx5: fix layer flags missing in metadata
6e77151286 Suanming Mou net/mlx5: fix match information in meter
792e749e92 Suanming Mou net/mlx5: fix register usage in meter
50f576d657 Suanming Mou net/mlx5: fix VLAN actions in meter
0654d4a8ad Thomas Monjalon app/testpmd: fix hot-unplug detaching
next reply other threads:[~2020-02-27 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 10:07 luca.boccassi [this message]
2020-03-02 10:52 ` 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=20200227100702.685-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).