patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please check if patch 'net/cxgbe: fix other misc build issues for Windows' is applicable to LTS release 17.11.6
Date: Tue, 12 Mar 2019 21:28:11 +0000	[thread overview]
Message-ID: <3D4EDEBE-FD9A-4B00-BDA2-7E0EA0026CF9@mellanox.com> (raw)
In-Reply-To: <20190310101350.GB1197@chelsio.com>


> On Mar 10, 2019, at 3:13 AM, Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> wrote:
> 
> On Friday, March 03/08/19, 2019 at 23:39:01 +0530, Yongseok Koh wrote:
>> Hi,
>> 
>> Even though the patch doesn't have "Cc: stable@dpdk.org" tag or "Fixes:" tag,
>> the commit log says it fixes some issue. Tags might be mistakenly missed. We
>> don't want to miss any fixes for stable releases. That's why I'm sending this
>> email.
>> 
>> Please send backports if you think the patch should be merged to LTS release 17.11.6
>> Or, let me know if you have any comments, say, need more time, or it's worthless
>> to backport it. And please send it to "stable@dpdk.org", but not "dev@dpdk.org".
>> 
>> 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: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk.org%2Fbrowse%2Fdpdk-stable%2Fcommit%2F%3Fh%3D16.07%26id%3Dc4831394c7d1944d8ec27d52c22997f20d19718e&amp;data=02%7C01%7Cyskoh%40mellanox.com%7C557b5b77ae9d4d67632e08d6a5418ea6%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636878098323509754&amp;sdata=sQgQqWONbvvx0sM34wJlz%2B8qiBlWmnaMdS%2FSohty%2B7E%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 17.11] foo/bar: fix baz
>> 
>> With git send-email, this can be achieved by appending the parameter:
>> 
>>    --subject-prefix='17.11'
>> 
>> 
>> Thanks.
>> 
>> Yongseok
>> 
> 
> Don't backport this patch. It fixes compilation errors reported by
> Intel C++ Compiler for the upcoming DPDK Windows OS support, and
> hence is unnecessary to backport to older stable releases that don't
> have DPDK Windows OS support.

Thanks for confirming.
Yongseok

  reply	other threads:[~2019-03-12 21:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 18:08 [dpdk-stable] please check if patch 'eal: fix strdup usages in internal config' " Yongseok Koh
2019-03-08 18:09 ` [dpdk-stable] please check if patch 'net/cxgbe: fix macros related to logs for Windows' " Yongseok Koh
2019-03-10 10:13   ` Rahul Lakkireddy
2019-03-08 18:09 ` [dpdk-stable] please check if patch 'net/cxgbe: fix other misc build issues " Yongseok Koh
2019-03-10 10:13   ` Rahul Lakkireddy
2019-03-12 21:28     ` Yongseok Koh [this message]
2019-03-11 10:08 ` [dpdk-stable] please check if patch 'eal: fix strdup usages in internal config' " Burakov, Anatoly
2019-03-12 21:43   ` 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=3D4EDEBE-FD9A-4B00-BDA2-7E0EA0026CF9@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=rahul.lakkireddy@chelsio.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).