From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from office2.cesnet.cz (office2.cesnet.cz [195.113.144.244]) by dpdk.org (Postfix) with ESMTP id 38B552A5B; Tue, 24 Jan 2017 17:05:23 +0100 (CET) Received: from [IPv6:2001:67c:1220:80c:f8f4:f055:211e:fe80] (unknown [IPv6:2001:67c:1220:80c:f8f4:f055:211e:fe80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by office2.cesnet.cz (Postfix) with ESMTPSA id BC895200E8; Tue, 24 Jan 2017 17:05:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=office2; t=1485273922; bh=8IWf5idDInJDDCRBbcyrwSjyIJAfqSKRu1tVxAReYD8=; h=Subject:To:References:From:Cc:Date:In-Reply-To; b=f1l/ZxS+EPAW2xdawVbckZv2Dr+USAfHyEhbOL9467L++4H0LuSueCTW20El9B80Y 8WjzvQy/Xs2pbHbhUXc0MY1wJ9hEe0yfUxW+FvDq7RKb5wP3C4qTckf8FXJU1tDfZD A/8IFi4n0nl6zSkCzJKSiHSrvMXayBlcbrVt7DBU= To: Ferruh Yigit References: <1485254992-12545-1-git-send-email-vido@cesnet.cz> <9b70ce3e-d4c6-aad3-bbcf-37c27b0eac3a@intel.com> From: Matej Vido Cc: dev@dpdk.org, dpdk stable Message-ID: <48bb90a9-0a43-253b-720d-21f6a3d53f20@cesnet.cz> Date: Tue, 24 Jan 2017 17:05:23 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <9b70ce3e-d4c6-aad3-bbcf-37c27b0eac3a@intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] net/szedata2: fix incorrect device memory access X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2017 16:05:23 -0000 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 > Reviewed-by: Ferruh Yigit > > 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? Thanks, Matej