DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Matej Vido <vido@cesnet.cz>
Cc: dev@dpdk.org, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/szedata2: fix incorrect device memory access
Date: Tue, 24 Jan 2017 16:29:35 +0000	[thread overview]
Message-ID: <f0f883c1-1f54-cbf1-90a5-efd69ca50acf@intel.com> (raw)
In-Reply-To: <48bb90a9-0a43-253b-720d-21f6a3d53f20@cesnet.cz>

On 1/24/2017 4:05 PM, Matej Vido wrote:
> On 24.01.2017 16:24, Ferruh Yigit wrote:
>> On 1/24/2017 10:49 AM, Matej Vido wrote:
>>> Fixes: 8acba705b119 ("net/szedata2: localize handling of PCI resources")
>>>
>>> Signed-off-by: Matej Vido <vido@cesnet.cz>
>> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>>
>> Cc: stable@dpdk.org
>>
>> Applied to dpdk-next-net/master, thanks.
> I'm not sure about the policy regarding the stable releases, but I think 
> that this patch doesn't belong to stable as the bug was introduced and 
> also fixed during the current 17.02 window. Or am I wrong?

Yes you are right, I missed that issue introduced in this release, I
removed stable tag from commit log.

Thanks,
ferruh

> 
> Thanks,
> Matej
> 

      reply	other threads:[~2017-01-24 16:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 10:49 Matej Vido
2017-01-24 11:58 ` Ferruh Yigit
2017-01-24 14:02   ` Matej Vido
2017-01-24 14:17     ` Ferruh Yigit
2017-01-24 15:11     ` Ferruh Yigit
2017-01-24 15:55       ` Matej Vido
2017-01-24 16:03         ` Ferruh Yigit
2017-01-24 15:24 ` Ferruh Yigit
2017-01-24 16:05   ` Matej Vido
2017-01-24 16:29     ` Ferruh Yigit [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=f0f883c1-1f54-cbf1-90a5-efd69ca50acf@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=vido@cesnet.cz \
    /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).