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]
Message-ID: <535739d8-b8a5-5edd-9bba-e432be02e2da@gmail.com>
Date:   Mon, 26 Aug 2019 20:23:43 +0200
From:   Jacek Anaszewski <jacek.anaszewski@...il.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Dan Murphy <dmurphy@...com>
Subject: Re: linux-next: Fixes tag needs some work in the leds tree

Hi Stephen,

Thank you for the notification.

On 8/25/19 11:19 PM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   3f5381c2ba60 ("leds: lm3532: Fixes for the driver for stability")
> 
> Fixes tag
> 
>   Fixes: e37a7f8d77e1 ("leds: lm3532: Introduce the lm3532 LED driver")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> In commit
> 
>   c4b8354e5341 ("leds: lm3532: Fix brightness control for i2c mode")
> 
> Fixes tag
> 
>   Fixes: e37a7f8d77e1 ("leds: lm3532: Introduce the lm3532 LED driver")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Did you mean
> 
> Fixes: bc1b8492c764 ("leds: lm3532: Introduce the lm3532 LED driver")
> 

Tags should now be correct.

-- 
Best regards,
Jacek Anaszewski

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ