From: Luca Boccassi <bluca@debian.org>
To: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.3
Date: Wed, 03 Jun 2020 09:48:18 +0100 [thread overview]
Message-ID: <47184ba0887185706206a56147f51e1f54dada99.camel@debian.org> (raw)
In-Reply-To: <0f72a373ea18930a93dfbfa8cb4579b7577727a8.camel@gmail.com>
On Wed, 2020-05-27 at 17:10 +0100, Luca Boccassi wrote:
> 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 June the 3rd.
>
>
> 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
>
> ---
> 96477b5dd5 Ajit Khaparde net/bnxt: fix allocation of COS queue info
> 205b742952 Ajit Khaparde net/bnxt: fix allocation of LED config info
> 986fa3ba83 Ajit Khaparde net/bnxt: fix allocation of link info struct
> e8fe0e067b Ajit Khaparde net/bnxt: fix allocation of PF info struct
> 29fdc5bf45 Apeksha Gupta test/crypto: fix statistics case
> fb94f35948 Chengchang Tang net/hns3: fix adding multicast MAC address
> a4e6ea97a5 Dekel Peled common/mlx5: fix RSS key copy to TIR context
> 1db72630da Dmitry Kozlyuk eal/windows: do not expose private facilities
> 867b49d17a Ferruh Yigit ring: fix build for gcc O1 optimization
> 48f9faddc6 Kalesh AP net/bnxt: fix MAC address setting when port is stopped
> 10d6982008 Kalesh AP net/bnxt: fix recovery alarm race condition in port close
> 920be799db Lijun Ou net/hns3: fix RSS indirection table configuration
> 5af61440dd Matan Azrad net/mlx5: fix flow counter container resize
> 6e585db689 Michal Krawczyk net/ena/base: fix testing for supported hash function
> f5bf02df31 Ori Kam eal/ppc: fix bool type after altivec include
> dede694cd5 Pablo de Lara doc: add NASM installation steps
> 0aa1ab2fb4 Qi Zhang net/ice/base: fix a couple of casting
> a7b645debc Qi Zhang net/ice/base: fix DCF switch rule
> a1f5c1c27c Qi Zhang net/ice/base: fix removing MAC rule
> 3ccf61bc1e Qi Zhang net/ice/base: fix tunnel type match word handling
> a60704d1ac Rasesh Mody net/qede: fix assignment of Rx/Tx handlers
> 4448a202b6 Thomas Monjalon eal: remove useless makefiles
Thanks to those who sent out backports.
Last chance for letting me know if you intend to provide more backports
for any of the above - I will be tagging rc1 this evening.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2020-06-03 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 16:10 Luca Boccassi
2020-06-03 8:48 ` Luca Boccassi [this message]
[not found] <20200527101401.274945-1-luca.boccassi@gmail.com>
2020-05-28 9:29 ` Wei Hu (Xavier)
2020-05-28 16:35 ` Luca Boccassi
2020-05-29 3:38 ` Wei Hu (Xavier)
2020-06-05 12:49 ` Ferruh Yigit
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=47184ba0887185706206a56147f51e1f54dada99.camel@debian.org \
--to=bluca@debian.org \
--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).