From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Herbert Xu" <herbert@gondor.apana.org.au>
Cc: "Akhil R" <akhilrajeev@nvidia.com>, <davem@davemloft.net>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<linux-crypto@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
"Dragan Simic" <dsimic@manjaro.org>,
"Corentin Labbe" <clabbe@baylibre.com>,
<linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 00/10] Tegra Security Engine driver improvements
Date: Sat, 19 Apr 2025 11:48:46 +0200 [thread overview]
Message-ID: <D9AIRPBIHXAO.3SDHEJW99DP4X@cknow.org> (raw)
In-Reply-To: <aAMhYaq0Ze-z6E8q@gondor.apana.org.au>
[-- Attachment #1.1: Type: text/plain, Size: 472 bytes --]
On Sat Apr 19, 2025 at 6:06 AM CEST, Herbert Xu wrote:
> On Fri, Apr 18, 2025 at 01:45:23PM +0200, Diederik de Haas wrote:
>>
>> Earlier today I tried to boot my 6.15-rc1 kernel on my RockPro64
>> (rk3399) and that didn't go too well:
>
> This should be fixed in the latest mainline kernel where hash
> request chaining has been disabled.
Excellent, thanks for letting me know.
b2e689baf220 ("crypto: ahash - Disable request chaining")
Cheers,
Diederik
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2025-04-19 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250224091610.49683-1-akhilrajeev@nvidia.com>
2025-04-18 11:45 ` [PATCH v3 00/10] Tegra Security Engine driver improvements Diederik de Haas
2025-04-19 4:06 ` Herbert Xu
2025-04-19 9:48 ` Diederik de Haas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D9AIRPBIHXAO.3SDHEJW99DP4X@cknow.org \
--to=didi.debian@cknow.org \
--cc=akhilrajeev@nvidia.com \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=dsimic@manjaro.org \
--cc=herbert@gondor.apana.org.au \
--cc=jonathanh@nvidia.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox