From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <yuanhan.liu@linux.intel.com>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
 by dpdk.org (Postfix) with ESMTP id B72313238
 for <stable@dpdk.org>; Wed,  9 Nov 2016 06:38:30 +0100 (CET)
Received: from fmsmga006.fm.intel.com ([10.253.24.20])
 by fmsmga104.fm.intel.com with ESMTP; 08 Nov 2016 21:38:29 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.31,612,1473145200"; d="scan'208";a="29047191"
Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162])
 by fmsmga006.fm.intel.com with ESMTP; 08 Nov 2016 21:38:28 -0800
Date: Wed, 9 Nov 2016 13:39:18 +0800
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Cc: stable@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>
Message-ID: <20161109053918.GM12283@yliu-dev.sh.intel.com>
References: <cover.1478600855.git.nelio.laranjeiro@6wind.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cover.1478600855.git.nelio.laranjeiro@6wind.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: [dpdk-stable] [PATCH 00/14] Patches for 16.07.2 stable branch
X-BeenThere: stable@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches for 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: Wed, 09 Nov 2016 05:38:31 -0000

On Tue, Nov 08, 2016 at 11:36:41AM +0100, Nelio Laranjeiro wrote:
> Patchset of fixes from 16.11 master branch rebased on top of 16.07.1 tag.

Hi Nelio,

I appreciate your help here! However, would you do the rebase on top of
the 16.07 branch? I have already cherry-picked few patches there for
16.07.2:

    [yliu@yliu-dev ~/dpdk]$ git log --oneline v16.07.1..HEAD -- drivers/net/mlx5
    23641e8 net/mlx5: fix link status report
    da181ce net/mlx5: fix hash key size retrieval
    c1097f4 net/mlx5: fix Rx function selection

Besides, would you add a heading line before the commit log body if it's
a commit cherry-picked from master branch?

    [ upstream commit xxx ]

And add following if it can't be applied cleanly that needs backport
effort?

    [ backported from upstream commit xxx]

Thanks.

	--yliu