From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <yliu@fridaylinux.org>
Received: from mail-pg0-f49.google.com (mail-pg0-f49.google.com [74.125.83.49])
 by dpdk.org (Postfix) with ESMTP id 001D92BEF
 for <stable@dpdk.org>; Mon, 21 Aug 2017 05:40:18 +0200 (CEST)
Received: by mail-pg0-f49.google.com with SMTP id n4so28021836pgn.1
 for <stable@dpdk.org>; Sun, 20 Aug 2017 20:40:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=fridaylinux-org.20150623.gappssmtp.com; s=20150623;
 h=date:from:to:cc:subject:message-id:references:mime-version
 :content-disposition:in-reply-to:user-agent;
 bh=kDICELk6y5zezl0x1jmG62xH8d+JnzKTn2/xY2curIU=;
 b=BTv+rGIWA3hwepWprGTjEzJu1E/MnBaPalZUjdYodhPJ3bTYQ/KIEOBuZOZE/TAkYw
 cMVI/2EeQmqID6Zmg1DSG/PWqtZr2UU59+JFWdfA2kCy+pZyHmRpXUneJjWLXt6fpINw
 18RPS0UMnest2ZbwKBaLsWr2lrnpywDgzNqVcA5vT2DaFz8MeqEl6eV5buBcCzRYR8Dx
 lwThNxfX5FPL9zRdbwzE+0bjouf1XO4G7+2TKXpmxcF/Z0ZMtKMA7AQzmqoG3zdfUdoG
 Bv15IT2JAXIrCVL8bh/8VL8vhDk+OVDcYXcT8fdRclcKgxYew7yi82sgAUMVZ/vsZMoH
 gG/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:references
 :mime-version:content-disposition:in-reply-to:user-agent;
 bh=kDICELk6y5zezl0x1jmG62xH8d+JnzKTn2/xY2curIU=;
 b=L+HCl5YedeczpcV2DWzMJ3Q+R9O6TmbN9wXfBJ0rc3r6707QH/sYrESWPAbdMSHrkE
 nlw73DS6Qo26RfS5MZu2C0euCmGCNtV5ScgIG2C9ngou/ogtRCp0IGMWe1FgpG7WaM5P
 +eEDb7zidxBO/lwxe6IYfhd90U0Y07zAEzN2eJW+NCzOmodE3SmVaZ94QzI7orJLxena
 rV1sVzkEuMi6mJxyMCxHLQ78IdSw6Vjz6G04/uQ/HSKFVypQ8SImf3NBcxE94lhN7jU8
 ZFu/2+CTEE70JmNmyfTzkW45ZwV/qrw0/mlSbXQ++LbdAYeNoSbNjj4jK+blRGnTFJ7M
 7zpQ==
X-Gm-Message-State: AHYfb5iDFu1EPPTX/tKRD4RjEIlp7MflE3SsGqOCri2DiS07wlCQZKvG
 WXTS0SicXe9IVnA4
X-Received: by 10.84.218.3 with SMTP id q3mr17564571pli.282.1503286818022;
 Sun, 20 Aug 2017 20:40:18 -0700 (PDT)
Received: from yliu-home ([45.63.61.64])
 by smtp.gmail.com with ESMTPSA id c80sm8449677pfj.26.2017.08.20.20.40.15
 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Sun, 20 Aug 2017 20:40:16 -0700 (PDT)
Date: Mon, 21 Aug 2017 11:40:11 +0800
From: Yuanhan Liu <yliu@fridaylinux.org>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dpdk stable <stable@dpdk.org>, dev@dpdk.org
Message-ID: <20170821034011.GO9612@yliu-home>
References: <20170818104545.GN9612@yliu-home>
 <c9b5eef5-9b7c-2b86-c637-e75a1e386fed@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c9b5eef5-9b7c-2b86-c637-e75a1e386fed@redhat.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Subject: Re: [dpdk-stable] 16.11.3 (LTS) patches review and test
X-BeenThere: stable@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches for DPDK stable branches <stable.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/stable>,
 <mailto:stable-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/stable/>
List-Post: <mailto:stable@dpdk.org>
List-Help: <mailto:stable-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/stable>,
 <mailto:stable-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Aug 2017 03:40:19 -0000

On Fri, Aug 18, 2017 at 06:29:02PM +0100, Kevin Traynor wrote:
> On 08/18/2017 11:45 AM, Yuanhan Liu wrote:
> > Hi all,
> > 
> > Here is a list of patches targeted for LTS release 16.11.3. Please
> > help review and test. The planned date for the final release is 30th,
> > Aug. Before that, please let me know if anyone has objections with
> > these patches being applied.
> > 
> > These patches are located at branch 16.11 of dpdk-stable repo:
> >     http://dpdk.org/browse/dpdk-stable/
> > 
> > Thanks.
> > 
> >         --yliu
> > 
> 
> Hi Yuanhan,
> 
> I think this one should go in too, as OVS hits this and writes back the
> wrong watermark value to the shared register which can cause problems
> for other ports. I've applied and tested it with DPDK 16.11.
> 
> commit 0e61ab56e01655f02bfe4e6249e032e864b0f5dd
> Author: Qi Zhang <qi.z.zhang@intel.com>
> Date:   Thu Aug 10 18:48:07 2017 +0800
> 
>     net/i40e: fix flow control watermark mismatch
> 
>     Flow control watermark is not read out correctly,
>     that may cause an application who not intend to change
>     watermark but does change it with a rte_eth_dev_flow_ctrl_set
>     call right after rte_eth_dev_flow_ctrl_get.

Weird, I couldn't find this commit:

    $ git show 0e61ab56e01655f02bfe4e6249e032e864b0f5dd
    fatal: bad object 0e61ab56e01655f02bfe4e6249e032e864b0f5dd

	--yliu