From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wang Weidong <wangweidong1@huawei.com>
Subject: Re: [PATCH net-next 0/2] tipc: do some fixups
Date: Wed, 25 Dec 2013 09:33:04 +0800
Message-ID: <52BA35D0.7060003@huawei.com>
References: <1387263827-20876-1-git-send-email-wangweidong1@huawei.com> <20131224.174541.2213038026686672610.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: <jon.maloy@ericsson.com>, <allan.stephens@windriver.com>,
	<David.Laight@ACULAB.COM>, <netdev@vger.kernel.org>
To: David Miller <davem@davemloft.net>
Return-path: <netdev-owner@vger.kernel.org>
Received: from szxga02-in.huawei.com ([119.145.14.65]:55782 "EHLO
	szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751158Ab3LYBd1 (ORCPT
	<rfc822;netdev@vger.kernel.org>); Tue, 24 Dec 2013 20:33:27 -0500
In-Reply-To: <20131224.174541.2213038026686672610.davem@davemloft.net>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On 2013/12/25 6:45, David Miller wrote:
> 
> Referring to commit purely by SHA1 ID is ambiguous.
> 
> If the change is placed in other trees, such as the -stable
> branches, they will have different SHA1 IDs.
> 
> This is why you must always refer to commits as the
> SHA1 ID followed by the commit header line text of
> the commit in parenthesis and double quotes, like
> this:
> 
> Commit 0cee6bbe06f ("tipc: remove unnecessary variables and conditions")
> 
> Please fix this up in this entire patch series and resubmit.
> 
Ok, I will fix them.

Regards.
Wang

>