[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0077259b-11bb-107c-97ea-ad739e1d2e86@embeddedor.com>
Date: Thu, 18 Oct 2018 08:24:02 +0200
From: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To: Kees Cook <keescook@...omium.org>
Cc: Antoine Tenart <antoine.tenart@...tlin.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
linux-crypto <linux-crypto@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] crypto: inside-secure: safexcel - fix memory allocation
On 10/17/18 8:23 PM, Kees Cook wrote:
>>
>> If so, could you take this patch?
>
> Since this has no functional exposure (the sizes are the same), let's
> just wait until after the merge window to get this into crypto-next.
>
Okay. I agree.
Thanks!
--
Gustavo
Powered by blists - more mailing lists