netdev - Re: [PATCH net-next 0/2] tipc: do some fixups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <52BA35D0.7060003@huawei.com>
Date:	Wed, 25 Dec 2013 09:33:04 +0800
From:	Wang Weidong <wangweidong1@...wei.com>
To:	David Miller <davem@...emloft.net>
CC:	<jon.maloy@...csson.com>, <allan.stephens@...driver.com>,
	<David.Laight@...LAB.COM>, <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 0/2] tipc: do some fixups

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

> 


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html