[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<PH7PR12MB817817C71B80A04A82CEEF1EC0102@PH7PR12MB8178.namprd12.prod.outlook.com>
Date: Mon, 6 Jan 2025 04:11:02 +0000
From: Akhil R <akhilrajeev@...dia.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
CC: "davem@...emloft.net" <davem@...emloft.net>, "thierry.reding@...il.com"
<thierry.reding@...il.com>, Jon Hunter <jonathanh@...dia.com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/7] crypto: tegra: Use separate buffer for setkey
, Dec 31, 2024 at 04:25:06AM +0000, Akhil R wrote:
> >
> > Does it sound good, or do you think it will make the code overly complicated?
>
> My main concern was arbitrary failure when you exceeded the 16-slot
> limit. As long as that problem goes away I'm happy with any solution.
Thanks. I will send out a patch for this along with the other changes as the next version.
Any concerns on the other patches in the series? I can push the updates together in
the next version, if anything.
Thanks,
Akhil
Powered by blists - more mailing lists