linux-kernel - Re: linux-next: Fixes tag needs some work in the selinux 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <a7adaaab-cbc3-06ce-f3ab-b411598414e8@infradead.org>
Date:   Mon, 13 Jun 2022 20:41:00 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Paul Moore <paul@...l-moore.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the selinux tree



On 6/13/22 16:33, Paul Moore wrote:
> On Mon, Jun 13, 2022 at 6:24 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>
>> Hi all,
>>
>> In commit
>>
>>   e81ee824e8a1 ("docs: selinux: add '=' signs to kernel boot options")
>>
>> Fixes tag
>>
>>   Fixes: ^1da177e4c3f4 ("Linux-2.6.12-rc2")
>>
>> has these problem(s):
>>
>>   - No SHA1 recognised
>>
>> Also, I don't think that is a relevent or useful Fixes tag anyway.
> 
> Good point Stephen.  I just dropped the tag in the offending commit
> and did a force push back to selinux/next; sorry for the noise.
> 

Thanks Stephen and Paul.

-- 
~Randy