From: Jeff Barnes <jeffbarnes@linux.microsoft.com>
To: horia.geanta@nxp.com, pankaj.gupta@nxp.com, gaurav.jain@nxp.com,
herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] crypto: caam - fix in-place RSA payload DMA mapping
Date: Tue, 10 Nov 2026 18:19:23 -0500 [thread overview]
Message-ID: <20261110231923.165037-1-jeffbarnes@linux.microsoft.com> (raw)
In-Reply-To: <20261020192511.3389133-1-jeffbarnes@linux.microsoft.com>
Gentle ping on this RFC.
I would appreciate any feedback on the DMA mapping approach, particularly whether a single DMA_BIDIRECTIONAL mapping is the right model for the exact source/destination alias case.
Thanks,
Jeff
prev parent reply other threads:[~2026-11-10 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 19:25 Jeff Barnes
2026-10-20 19:25 ` [RFC PATCH 1/1] " Jeff Barnes
2026-11-10 23:19 ` Jeff Barnes [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=20261110231923.165037-1-jeffbarnes@linux.microsoft.com \
--to=jeffbarnes@linux.microsoft.com \
--cc=davem@davemloft.net \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@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®