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:   Wed, 12 Oct 2022 07:42:32 -0500
From:   Mario Limonciello <mario.limonciello@....com>
To:     Herbert Xu <herbert@...dor.apana.org.au>
Cc:     "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "Thomas, Rijo-john" <Rijo-john.Thomas@....com>,
        "David S. Miller" <davem@...emloft.net>,
        "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Lendacky, Thomas" <Thomas.Lendacky@....com>,
        "Allen, John" <John.Allen@....com>
Subject: Re: [PATCH] crypto: ccp: Add support for TEE for PCI ID 0x14CA

On 10/12/22 04:31, Herbert Xu wrote:
> On Fri, Oct 07, 2022 at 08:24:06PM +0000, Limonciello, Mario wrote:
>>
>> I noticed you sent out the 6.1 PR already.  So I Just wanted to make sure this
>> didn't get overlooked as it's already got a T-b/A-b.
> 
> Hi Mario:
> 
> This didn't make the deadline for inclusion in my 6.1 PR.  Is there
> any reason why it has to go in this merge window rather than the next?
> 
> Thanks,

Some other maintainers take new IDs as fixes.  Particularly when they're 
good candidates for cc stable.

The main reason I wanted to see it sooner is so that it has more time to 
percolate to the various downstream distros so that errors stemming from 
the lack of this ID declaration aren't prevalent when using this SOC.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ