patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 18.02.2
Date: Mon, 30 Apr 2018 16:44:38 +0100	[thread overview]
Message-ID: <1525103078.23337.26.camel@debian.org> (raw)
In-Reply-To: <99846f47-bd43-67f1-8dce-84519c9823b8@redhat.com>

On Mon, 2018-04-30 at 17:30 +0200, Maxime Coquelin wrote:
> 
> On 04/30/2018 05:23 PM, luca.boccassi@gmail.com wrote:
> > Hi commit authors (and maintainers),
> > 
> > I didn't manage to apply following commits from upstream to stable
> > branch
> > 18.02: conflict happens. I'm wondering can the authors check the
> > following
> > list and backport those patches belong to you?
> > 
> > FYI, branch 18.02 is located at tree:
> >     git://dpdk.org/dpdk-stable
> > 
> > It'd be great if you could do that before Friday, if necessary.
> > Also, please add a
> > heading line like below before the commit log body:
> >      [ backported from upstream commit xxx ]
> > 
> > Example:http://dpdk.org/browse/dpdk-stable/commit/?h=16.07&id=c4831
> > 394c7d1944d8ec27d52c22997f20d19718e
> > 
> > Also please mention the target stable in the subject line, as we
> > have more than one
> > at the same time, for example:
> > 
> >      [PATCH 18.02] foo/bar: fix baz
> > 
> > With git send-email, this can be achieved by appending the
> > parameter:
> > 
> >      --subject-prefix='18.02'
> > 
> > Please let me know if you have any comments, say, need more time,
> > or it's
> > worthless to packport it. And please send it to"stable@dpdk.org",
> > but not
> > "dev@dpdk.org".
> > 
> > Thanks.
> > 
> > Luca Boccassi
> > 
> > ---
> 
> ...
> > c6ae7de0d  Maxime Coquelin  vhost: fix indirect descriptors table
> > translation size
> 
> This one is already backported in v18.02.1, as it was part of the CVE
> series:

Sorry, forgot there was a reason I skipped that one :-)

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2018-04-30 15:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 15:23 luca.boccassi
2018-04-30 15:30 ` Maxime Coquelin
2018-04-30 15:44   ` Luca Boccassi [this message]
2018-04-30 16:06 ` Burakov, Anatoly
2018-04-30 16:33   ` Luca Boccassi
2018-05-02  6:04 ` Hyong Youb Kim
2018-05-02 10:43   ` Luca Boccassi
2018-05-02  8:27 ` Nélio Laranjeiro
2018-05-02 10:42   ` Luca Boccassi
2018-05-18  9:46 ` luca.boccassi
2018-05-18 10:11   ` Richardson, Bruce
2018-05-18 10:21     ` Luca Boccassi
2018-05-18 10:25   ` Andy Green
2018-05-18 10:33     ` Pattan, Reshma
2018-05-18 10:36       ` Andy Green
2018-05-18 11:37   ` [dpdk-stable] [PATCH 0/5] 18.02 Requested backports Andy Green
2018-05-18 11:37     ` [dpdk-stable] [PATCH 1/5] eal: support strlcpy function Andy Green
2018-05-18 11:37     ` [dpdk-stable] [PATCH 2/5] bus/pci: fix size of driver name buffer Andy Green
2018-05-18 11:38     ` [dpdk-stable] [PATCH 3/5] net/qede: fix strncpy Andy Green
2018-05-18 11:38     ` [dpdk-stable] [PATCH 4/5] net/qede: replace strncpy by strlcpy Andy Green
2018-05-18 11:38     ` [dpdk-stable] [PATCH 5/5] net/sfc: make sure that stats name is nul-terminated Andy Green
2018-05-18 13:13     ` [dpdk-stable] [PATCH 0/5] 18.02 Requested backports Luca Boccassi
2018-05-25 17:23   ` [dpdk-stable] please help backporting some patches to stable release 18.02.2 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=1525103078.23337.26.camel@debian.org \
    --to=bluca@debian.org \
    --cc=maxime.coquelin@redhat.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).