From: Herbert Xu <herbert@gondor.apana.org.au>
To: Jeff Barnes <jeffbarnes@linux.microsoft.com>
Cc: horia.geanta@nxp.com, pankaj.gupta@nxp.com, gaurav.jain@nxp.com,
davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sahil Malhotra <sahil.malhotra@nxp.com>
Subject: Re: [RFC PATCH 1/1] crypto: caam - fix in-place RSA payload DMA mapping
Date: Wed, 11 Nov 2026 18:54:19 +0800 [thread overview]
Message-ID: <avRJW9494fF7Pyf4@gondor.apana.org.au> (raw)
In-Reply-To: <20261020192511.3389133-2-jeffbarnes@linux.microsoft.com>
On Tue, Oct 20, 2026 at 03:25:11PM -0400, Jeff Barnes wrote:
> CAAM can receive RSA requests whose effective source and destination
> scatterlists are identical. The driver currently maps the source with
> DMA_TO_DEVICE and then maps the destination with DMA_FROM_DEVICE.
Sashiko has some comments on this patch:
https://sashiko.dev/#/patchset/20261020192511.3389133-1-jeffbarnes%40linux.microsoft.com
Please also explain how your patch interacts with the other
patches on caam:
https://patchwork.kernel.org/project/linux-crypto/list/?series=1189382
In any case, as I said in reply to the other patches, unless
the caam maintainers step up I think this should just be removed.
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
next prev parent reply other threads:[~2026-11-11 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 19:25 [RFC PATCH 0/1] " Jeff Barnes
2026-10-20 19:25 ` [RFC PATCH 1/1] " Jeff Barnes
2026-11-11 10:54 ` Herbert Xu [this message]
2026-11-10 23:19 ` [RFC PATCH 0/1] " Jeff Barnes
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=avRJW9494fF7Pyf4@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=gaurav.jain@nxp.com \
--cc=horia.geanta@nxp.com \
--cc=jeffbarnes@linux.microsoft.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=sahil.malhotra@nxp.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
all inboxes | Powered by JetHome®