patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Xueming Li <xuemingl@nvidia.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 20.11.1
Date: Thu, 18 Feb 2021 09:41:30 +0000	[thread overview]
Message-ID: <0f473ae83d7b291500c8fcd6e696aeac3ce16808.camel@debian.org> (raw)
In-Reply-To: <20210209103903.467789-1-luca.boccassi@gmail.com>

On Tue, 2021-02-09 at 10:39 +0000, luca.boccassi@gmail.com wrote:
> Hi commit authors (and maintainers),
> 
> I didn't apply following commits from DPDK main to 20.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 20.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 02/16/21.
> 
> 
> 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 20.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 20.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 20.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> c27e64ee3e  Chengchang Tang  net/hns3: fix stats flip overflow
> 7f2a320df9  Huisong Li       net/hns3: fix query order of link status and link info
> 00984de533  Viacheslav Ovsiienko net/mlx5: fix Tx queue size created with DevX

Hi Xueming,

Could you please check with Viacheslav if this net/mlx5 backport is
needed and if it is going to be sent soon, or if I should proceed
without it?

Thanks!

-- 
Kind regards,
Luca Boccassi

  parent reply	other threads:[~2021-02-18  9:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210205115222.1287558-1-luca.boccassi@gmail.com>
2021-02-05 11:53 ` luca.boccassi
2021-02-09 10:39   ` luca.boccassi
2021-02-12 23:42     ` luca.boccassi
     [not found]       ` <20210212234341.256656-1-luca.boccassi@gmail.com>
2021-02-16 13:08         ` Wang, Haiyue
2021-02-16 13:22           ` Luca Boccassi
2021-02-18  9:41     ` Luca Boccassi [this message]
2021-02-18 13:33       ` Xueming(Steven) Li
2021-02-18 17:42         ` Luca Boccassi
     [not found]     ` <20210209103924.468111-1-luca.boccassi@gmail.com>
2021-02-20  6:49       ` Huisong Li
2021-02-19  8:59   ` Ferruh Yigit
2021-02-22 12:00     ` 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=0f473ae83d7b291500c8fcd6e696aeac3ce16808.camel@debian.org \
    --to=bluca@debian.org \
    --cc=stable@dpdk.org \
    --cc=xuemingl@nvidia.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).