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:   Tue, 14 Apr 2020 19:36:28 -0500
From:   Larry Finger <Larry.Finger@...inger.net>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Kalle Valo <kvalo@...eaurora.org>,
        Wireless <linux-wireless@...r.kernel.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
 wireless-drivers-next tree

On 4/14/20 5:08 PM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>    ec4d3e3a0545 ("b43legacy: Fix case where channel status is corrupted")
> 
> Fixes tag
> 
>    Fixes: 75388acd0cd8 ("add mac80211-based driver for legacy BCM43xx devices")
> 
> has these problem(s):
> 
>    - Subject does not match target commit subject
>      Just use
> 	git log -1 --format='Fixes: %h ("%s")'
> 

Stephan,

I do not understand what you want here. The subject describes what was fixed. 
The error has been in the driver since it was merged. The Fixes: line is a 
description of the commit that introduced the driver file with the error.

Larry

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ