patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Yongseok Koh <yskoh@mellanox.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 17.11.4
Date: Sun, 29 Jul 2018 05:59:25 +0000	[thread overview]
Message-ID: <DB7PR05MB44267EBC1CB070A3081178E4C3280@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180727024008.39497-1-yskoh@mellanox.com>

Hi Koh,

Friday, July 27, 2018 5:40 AM, Yongseok Koh:
> Peng <xiaoxin.peng@broadcom.com>; Yongseok Koh
> <yskoh@mellanox.com>
> Subject: please help backporting some patches to LTS release 17.11.4
> 
> Hi commit authors (and maintainers),
> 
> I didn't manage to apply following commits from upstream to stable branch
> 17.11: conflict happens. I'm wondering can the authors check the following
> list and backport those patches belong to you?
> 
> FYI, branch 17.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: http://dpdk.org/browse/dpdk-
> stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e
> 
> Also please mention the target LTS in the subject line, as we have more than
> one at the same time, for example:
> 
>     [PATCH 17.11] foo/bar: fix baz
> 
> With git send-email, this can be achieved by appending the parameter:
> 
>     --subject-prefix='17.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.
> 
> Yongseok

The below one is not relevant for 17.11, you can drop it.

> e46821e9f  Shahaf Shuler    net/mlx5: separate generic tunnel TSO from the
> standard one

  parent reply	other threads:[~2018-07-29  5:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180727024051epcas3p20e5aa80ae259e6d8d83d44d60fd32625@epcas3p2.samsung.com>
2018-07-27  2:40 ` Yongseok Koh
2018-07-27  7:42   ` Ilya Maximets
2018-07-27  9:23     ` Luca Boccassi
2018-07-27 16:25     ` Kevin Traynor
2018-07-27 16:46       ` Ilya Maximets
2018-07-27 17:24         ` Kevin Traynor
2018-07-27 17:32           ` Yongseok Koh
2018-07-29  5:59   ` Shahaf Shuler [this message]
2018-08-13 20:45 Yongseok Koh

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=DB7PR05MB44267EBC1CB070A3081178E4C3280@DB7PR05MB4426.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=yskoh@mellanox.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).