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: <67b5c37f-ff63-9ae5-fe80-0d2ac0821000@intel.com>
Date:   Wed, 8 Jan 2020 08:05:58 -0500
From:   Dennis Dalessandro <dennis.dalessandro@...el.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Doug Ledford <dledford@...hat.com>,
        Jason Gunthorpe <jgg@...lanox.com>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "Michael J. Ruhl" <michael.j.ruhl@...el.com>,
        Kaike Wan <kaike.wan@...el.com>
Subject: Re: linux-next: Fixes tag needs some work in the rdma tree

On 1/7/2020 3:33 PM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>    44ec5aa3c615 ("IB/hfi1: List all receive contexts from debugfs")
> 
> Fixes tag
> 
>    Fixes: bf808b5039c ("IB/hfi1: Add kernel receive context info to debugfs")
> 
> has these problem(s):
> 
>    - SHA1 should be at least 12 digits long
>      Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
>      or later) just making sure it is not set (or set to "auto").
> 

bf808b5039c

should be:

bf808b5039c6

A character got left off by mistake. Jason do you want to just fix this 
in your tree directly? Do we let it go and just make sure to catch it 
next time? Let me know if you want a new patch or something.

-Denny

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ