patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Matan Azrad <matan@nvidia.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.4
Date: Tue, 11 Aug 2020 18:57:05 +0100	[thread overview]
Message-ID: <20795c46933d003ab3829c8883c7df96d9278650.camel@debian.org> (raw)
In-Reply-To: <MW2PR12MB2492EEEB296BF2440EB67AC1DF450@MW2PR12MB2492.namprd12.prod.outlook.com>

On Tue, 2020-08-11 at 08:18 +0000, Matan Azrad wrote:
> Hi Luca
> From: luca.boccassi@gmail.com
> > 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 August the 17th.
> > If you'd like to backport the patches but cannot make it by the above
> > deadline, please let us know and we'll discuss whether the release can be
> > postponed.
> > 
> > 
> > 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
> > 
> > ---
> > 750ff30a8  Gregory Etelson  net/mlx5: fix tunnel flow priority
> > 71fa6a996  Jeff Guo         net/ice: fix hash action validation
> > 0466d286c  Kalesh AP        net/bnxt: fix setting link speed
> > d4d5a0411  Kalesh AP        net/bnxt: fix unnecessary memory allocation
> > 473d8e67d  Matan Azrad      common/mlx5: add virtio queue protection
> > domain
> > 04e7beeb1  Matan Azrad      vdpa/mlx5: adjust virtio queue protection
> > domain
> 
> The above 2 are for mlx5 vdpa driver which doesn't exist in 19.11 stable (added in 20.02).

Ok cool, thanks for letting me know.

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2020-08-11 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200810111818.61635-1-luca.boccassi@gmail.com>
2020-08-11  8:18 ` Matan Azrad
2020-08-11 17:57   ` Luca Boccassi [this message]
2020-08-12  3:44 ` Kalesh Anakkur Purayil
2020-08-13  6:10 ` Wang, ShougangX
2020-08-10 11:18 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=20795c46933d003ab3829c8883c7df96d9278650.camel@debian.org \
    --to=bluca@debian.org \
    --cc=matan@nvidia.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).