patches for DPDK stable branches
 help / color / mirror / Atom feed
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.1
Date: Mon, 02 Mar 2020 10:52:28 +0000	[thread overview]
Message-ID: <999f937f2d65f9dc97e8792cf7acae27d17c8c4b.camel@debian.org> (raw)
In-Reply-To: <20200227100702.685-1-luca.boccassi@gmail.com>

On Thu, 2020-02-27 at 10:07 +0000, luca.boccassi@gmail.com 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 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

All those patches (and more) have been provided by the teams - thank
you everybody! I will now proceed to tag -rc1 so that we can get
started with validation.

-- 
Kind regards,
Luca Boccassi

      reply	other threads:[~2020-03-02 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 10:07 luca.boccassi
2020-03-02 10:52 ` Luca Boccassi [this message]

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=999f937f2d65f9dc97e8792cf7acae27d17c8c4b.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).