From: LABBE Corentin <clabbe@baylibre.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
herbert@gondor.apana.org.au, heiko@sntech.de,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-sunxi@lists.linux.dev
Subject: Re: [RFC PATCH] crypto: flush poison data
Date: Wed, 6 Jul 2022 14:23:48 +0200 [thread overview]
Message-ID: <YsV+1DQzJ/KFnqBk@Red> (raw)
In-Reply-To: <20220706115807.GA16222@lst.de>
Le Wed, Jul 06, 2022 at 01:58:07PM +0200, Christoph Hellwig a écrit :
> On Wed, Jul 06, 2022 at 10:47:24AM +0100, Ben Dooks wrote:
> > I'm not sure that the dma-mapping code for non-coherent riscv systems
> > did get sorted. I couldn't find any when looking in 5.17.
>
> Yes, none of that is upstream. But as supporting it is essential for
> the allwinner SOCs I'm pretty sure Corentin is not actually using an
> upstream kernel anyway.
I use an upstream kernel + some "not yet merged but sent for review" patch serie like
"riscv: implement Zicbom-based CMO instructions + the t-head variant"
And good news, I just updated to use the v6 of this serie (just posted today) and my problem disappear.
Regards
next prev parent reply other threads:[~2022-07-06 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 13:27 [RFC PATCH] crypto: flush poison data Corentin Labbe
2022-07-01 13:35 ` Ben Dooks
2022-07-05 8:21 ` LABBE Corentin
2022-07-05 16:42 ` Christoph Hellwig
2022-07-05 17:56 ` LABBE Corentin
2022-07-05 17:58 ` Christoph Hellwig
2022-07-06 7:25 ` LABBE Corentin
2022-07-06 9:47 ` Ben Dooks
2022-07-06 11:58 ` Christoph Hellwig
2022-07-06 12:23 ` LABBE Corentin [this message]
2022-07-01 14:36 ` Andre Przywara
2022-07-01 14:55 ` LABBE Corentin
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=YsV+1DQzJ/KFnqBk@Red \
--to=clabbe@baylibre.com \
--cc=ben.dooks@codethink.co.uk \
--cc=hch@lst.de \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).