netdev - Re: [PATCH net-next] ibmvnic: Correct return code checking for ibmvnic

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] [day] [month] [year] [list]

Date:   Wed, 21 Jun 2017 15:52:31 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     nfont@...ux.vnet.ibm.com
Cc:     netdev@...r.kernel.org, jallen@...ux.vnet.ibm.com,
        tlfalcon@...ux.vnet.ibm.com
Subject: Re: [PATCH net-next] ibmvnic: Correct return code checking for
 ibmvnic_init during probe

From: Nathan Fontenot <nfont@...ux.vnet.ibm.com>
Date: Wed, 21 Jun 2017 14:48:06 -0500

> On 06/21/2017 02:39 PM, David Miller wrote:
>> From: Nathan Fontenot <nfont@...ux.vnet.ibm.com>
>> Date: Tue, 20 Jun 2017 17:21:54 -0400
>> 
>>> Fixes: 6a2fb0e99f9c (ibmvnic: driver initialization for kdump/kexec)
>> 
>> I'm incredibly curious where you got the idea to put the Fixes: tag
>> at the beginning of the commit message.
> 
> I have no excuse. As you mentioned I should have looked at what others
> had done when using the Fixes.
> 
> Would you like me to re-send with the Fixes tag corrected?

Yes, please.