From: Changwei Zou <changwei.zou@canonical.com>
To: herbert@gondor.apana.org.au
Cc: changwei.zou@canonical.com, davem@davemloft.net,
gaurav.jain@nxp.com, horia.geanta@nxp.com,
iuliana.prodan@nxp.com, jeffbarnes@linux.microsoft.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
lukas@wunner.de, martin.kepplinger-novakovic@ginzinger.com,
pankaj.gupta@nxp.com, sahil.malhotra@nxp.com,
sahil.malhotra@oss.nxp.com, stephane.debusne@cynove.com
Subject: [PATCH v6 0/2] crypto: caam - Fix RSA error-path unmap and unaligned dst buffers
Date: Fri, 20 Nov 2026 22:20:44 +1100 [thread overview]
Message-ID: <20261120112044.1174236-1-changwei.zou@canonical.com> (raw)
In-Reply-To: <awAS_kKAVkL2uWKT@gondor.apana.org.au>
Hi Herbert,
Thank you very much for your reviews across these versions, and for
pointing out the apply failure. v6 no longer applied after the upstream
caam_rsa_set_priv_key_form() changes (a91d9346a70b, 828c3b265b6d).
I have rebased the series onto the current tree and resubmitted as v7:
https://lore.kernel.org/linux-crypto/20261120110525.1170175-1-changwei.zou@canonical.com/
It is a rebase-only respin (no code changes); it also drops the
non-standard "Assisted-by:" trailer and carries Sahil Malhotra's
Reviewed-by on both patches.
Kind regards,
Changwei
prev parent reply other threads:[~2026-11-20 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 6:00 Changwei Zou
2026-11-14 6:00 ` [PATCH v6 1/2] crypto: caam - Fix wrong unmap operations Changwei Zou
2026-11-16 18:05 ` Sahil Malhotra
2026-11-14 6:00 ` [PATCH v6 2/2] crypto: caam - Use bounce buffer for unaligned RSA destination buffers Changwei Zou
2026-11-16 18:05 ` Sahil Malhotra
2026-11-18 23:13 ` Changwei Zou
2026-11-20 9:29 ` [PATCH v6 0/2] crypto: caam - Fix RSA error-path unmap and unaligned dst buffers Herbert Xu
2026-11-20 11:20 ` Changwei Zou [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=20261120112044.1174236-1-changwei.zou@canonical.com \
--to=changwei.zou@canonical.com \
--cc=davem@davemloft.net \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=iuliana.prodan@nxp.com \
--cc=jeffbarnes@linux.microsoft.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=martin.kepplinger-novakovic@ginzinger.com \
--cc=pankaj.gupta@nxp.com \
--cc=sahil.malhotra@nxp.com \
--cc=sahil.malhotra@oss.nxp.com \
--cc=stephane.debusne@cynove.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®