From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Rao, Nikhil" <nikhil.rao@intel.com>
Cc: dev@dpdk.org,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] eal: fix bug in x86 cmpset
Date: Thu, 29 Sep 2016 16:21:57 +0200 [thread overview]
Message-ID: <2741746.oWx263Rdf9@xps13> (raw)
In-Reply-To: <57ED141F.8020302@intel.com>
2016-09-29 18:46, Rao, Nikhil:
>
> On 9/29/2016 6:35 PM, Christian Ehrhardt wrote:
> > The patch misses a fixed: line which it should get I think.
>
> The bug has existed from the day the DPDK was open-sourced, i.e, there wasn't a specific
> commit that introduced this feature/bug, hence wasn't sure if it needed the fixes tag.
In this case, we use the first commit:
af75078 first public release
It means it can be backported everywhere.
prev parent reply other threads:[~2016-09-29 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1475184293-18298-1-git-send-email-nikhil.rao@intel.com>
2016-09-29 13:05 ` Christian Ehrhardt
2016-09-29 13:16 ` Rao, Nikhil
2016-09-29 14:21 ` Thomas Monjalon [this message]
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=2741746.oWx263Rdf9@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=nikhil.rao@intel.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).