netdev - Re: [PATCH] net/core: Add VF link state control policy

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: <20140610.204724.1766248023965511967.davem@davemloft.net>
Date:	Tue, 10 Jun 2014 20:47:24 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dledford@...hat.com
Cc:	sergei.shtylyov@...entembedded.com, netdev@...r.kernel.org,
	ronye@...lanox.com, ogerlitz@...lanox.com
Subject: Re: [PATCH] net/core: Add VF link state control policy

From: Doug Ledford <dledford@...hat.com>
Date: Tue, 10 Jun 2014 16:12:08 -0400

> On Wed, 2014-06-11 at 00:09 +0400, Sergei Shtylyov wrote:
>> Hello.
>> 
>> On 06/10/2014 11:59 PM, Doug Ledford wrote:
>> 
>> > Commit 1d8faf48c7 added VF link state control to the netlink VF nested
>> 
>>     Please also specify that commit's summary line in parens.
> 
> It was almost a carbon copy of my own commit summary:
> 
> (net/core: Add VF link state control)

But that is the way we absolutely require commits to be referred to,
SHA IDs are ambiguous, especially when changes are backported into
other trees.  Given that, the only unambiguous thing left is the
precise text of the commit header line.

That's why I require it to be explicitly provided alongside commit's
referred to in commit messages.
--
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