From: Herbert Xu <herbert@gondor.apana.org.au>
To: Nikolaus Voss <nikolaus.voss@haag-streit.com>
Cc: Horia Geanta <horia.geanta@nxp.com>,
Pankaj Gupta <pankaj.gupta@nxp.com>,
Gaurav Jain <gaurav.jain@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
David Gstir <david@sigma-star.at>,
Steffen Trumtrar <s.trumtrar@pengutronix.de>,
Nikolaus Voss <nv@vosn.de>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] crypto: caam: blob_gen.c: fix CAAM io mem access
Date: Fri, 30 Dec 2022 23:15:35 +0800 [thread overview]
Message-ID: <Y68Al6xfXj2ZvgHv@gondor.apana.org.au> (raw)
In-Reply-To: <20221220081750.2D0183BDB@mail.steuer-voss.de>
On Tue, Dec 20, 2022 at 09:17:50AM +0100, Nikolaus Voss wrote:
> IO memory access has to be done with accessors defined in caam/regs.h
> as there are little-endian architectures with a big-endian CAAM unit.
>
> Fixes: 6a83830f649a ("crypto: caam - warn if blob_gen key is insecure")
> Signed-off-by: Nikolaus Voss <nikolaus.voss@haag-streit.com>
> Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>
> ---
> v2: added upstream commit ref and reviewed-by line
>
> drivers/crypto/caam/blob_gen.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2022-12-30 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 8:17 Nikolaus Voss
2022-12-30 15:15 ` Herbert Xu [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=Y68Al6xfXj2ZvgHv@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=a.fatoum@pengutronix.de \
--cc=davem@davemloft.net \
--cc=david@sigma-star.at \
--cc=gaurav.jain@nxp.com \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikolaus.voss@haag-streit.com \
--cc=nv@vosn.de \
--cc=pankaj.gupta@nxp.com \
--cc=s.trumtrar@pengutronix.de \
/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
all inboxes | Powered by JetHome®