patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Shahaf Shuler <shahafs@mellanox.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.8
Date: Mon, 30 Jul 2018 09:54:17 +0100	[thread overview]
Message-ID: <1532940857.20916.35.camel@debian.org> (raw)
In-Reply-To: <DB7PR05MB44262F8F723BCD6A5AA67ED4C3280@DB7PR05MB4426.eurprd05.prod.outlook.com>

On Sun, 2018-07-29 at 06:03 +0000, Shahaf Shuler wrote:
> Hi Luca,
> 
> Thursday, July 26, 2018 6:32 PM, luca.boccassi:
> > Subject: please help backporting some patches to LTS release
> > 16.11.8
> > 
> > Hi commit authors (and maintainers),
> > 
> > I didn't manage to apply following commits from upstream to stable
> > branch
> > 16.11: conflict happens. I'm wondering can the authors check the
> > following
> > list and backport those patches belong to you?
> > 
> > FYI, branch 16.11 is located at tree:
> >    git://dpdk.org/dpdk-stable
> > 
> > It'd be great if you could do that in one or two weeks. Also,
> > please add a
> > heading line like below before the commit log body:
> >     [ backported from upstream commit xxx ]
> > 
> > Example:
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fd
> > pd
> > k.org%2Fbrowse%2Fdpdk-
> > stable%2Fcommit%2F%3Fh%3D16.07%26id%3Dc4831394c7d1944d8ec27d52c2
> > 2997f20d19718e&amp;data=02%7C01%7Cshahafs%40mellanox.com%7Cbb6e
> > 23a06b2c407bcda208d5f30cffe9%7Ca652971c7d2e4d9ba6a4d149256f461b%7
> > C0%7C0%7C636682159553329695&amp;sdata=2aATsk8VYml86NjW5%2BoEIJv
> > zeTqjaNfMDdTPui94xf4%3D&amp;reserved=0
> > 
> > Also please mention the target LTS in the subject line, as we have
> > more than
> > one at the same time, for example:
> > 
> >     [PATCH 16.11] foo/bar: fix baz
> > 
> > With git send-email, this can be achieved by appending the
> > parameter:
> > 
> >     --subject-prefix='16.11'
> > 
> > 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
> > 
> 
> The below one is not relevant for 16.11, you can drop it. 
> 
> > e46821e9f  Shahaf Shuler    net/mlx5: separate generic tunnel TSO
> > from the
> > standard one

Will do, thank you.

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2018-07-30  8:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 15:32 luca.boccassi
     [not found] ` <C6ECDF3AB251BE4894318F4E451236978247D952@IRSMSX109.ger.corp.intel.com>
2018-07-26 16:06   ` Luca Boccassi
2018-07-29  6:03 ` Shahaf Shuler
2018-07-30  8:54   ` Luca Boccassi [this message]
2018-07-30  9:13 ` luca.boccassi
2018-07-30 10:29   ` Burakov, Anatoly
2018-07-30 10:39     ` Luca Boccassi
2018-07-30 13:58   ` Rahul Lakkireddy
2018-07-30 16:02     ` Luca Boccassi
2018-08-08 15:19   ` 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=1532940857.20916.35.camel@debian.org \
    --to=bluca@debian.org \
    --cc=shahafs@mellanox.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).