On Fri, Jan 19, 2018 at 12:04:32PM +, Ard Biesheuvel wrote:
> This supersedes all outstanding patches from me related to SHA-3, SHA-512
> or SM-3.
>
> - fix a correctness issue in the SHA-3 code (#1) and a performance issue (#2),
> the first one is definitely a -stable candidate, the second
On 22 January 2018 at 20:51, Arnd Bergmann wrote:
> On Mon, Jan 22, 2018 at 3:54 PM, Arnd Bergmann wrote:
>> On Fri, Jan 19, 2018 at 1:04 PM, Ard Biesheuvel
>> I'm doing a little more randconfig build testing here now, will write back by
>> the end of today in the
On Mon, Jan 22, 2018 at 3:54 PM, Arnd Bergmann wrote:
> On Fri, Jan 19, 2018 at 1:04 PM, Ard Biesheuvel
> I'm doing a little more randconfig build testing here now, will write back by
> the end of today in the unlikely case that if I find anything else wrong.
Did a few hundred
On Fri, Jan 19, 2018 at 1:04 PM, Ard Biesheuvel
wrote:
> This supersedes all outstanding patches from me related to SHA-3, SHA-512
> or SM-3.
>
> - fix a correctness issue in the SHA-3 code (#1) and a performance issue (#2),
> the first one is definitely a -stable
This supersedes all outstanding patches from me related to SHA-3, SHA-512
or SM-3.
- fix a correctness issue in the SHA-3 code (#1) and a performance issue (#2),
the first one is definitely a -stable candidate, the second one potentially
as well
- patches #3 and #4 make the generic SHA-3 code