linux-kernel - Re: linux-next: Fixes tag needs some work in the hyperv-fixes tree

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]

Date:   Sun, 14 Jul 2019 08:02:11 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Sasha Levin <sashal@...nel.org>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the hyperv-fixes tree

On 7/14/19 5:55 AM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   2e6d7851bdeb ("PCI: pci-hyperv: fix build errors on non-SYSFS config")
> 
> Fixes tag
> 
>   Fixes: a15f2c08c708 ("PCI: hv: support reporting serial number as slot

oops, copy-paste error.

> 
> has these problem(s):
> 
>   - Subject has leading but no trailing parentheses
>   - Subject has leading but no trailing quotes
> 
> Please do not split Fixes tags over more than one line.  Also do not
> include blank lines among the tag lines.

Hm, so you are saying that the Fixes: line should not be separated from the
other tag lines?  That's news to me...
Should Fixes: be before the other tag lines or does it matter?

thanks.
-- 
~Randy