From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Denis Efremov <efremov@linux.com>
Cc: linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] crypto: amlogic - use kfree_sensitive()
Date: Thu, 27 Aug 2020 16:50:03 +0200 [thread overview]
Message-ID: <20200827145003.GA14173@Red> (raw)
In-Reply-To: <20200827064402.7130-3-efremov@linux.com>
On Thu, Aug 27, 2020 at 09:44:00AM +0300, Denis Efremov wrote:
> Use kfree_sensitive() instead of open-coding it.
>
> Signed-off-by: Denis Efremov <efremov@linux.com>
> ---
> drivers/crypto/amlogic/amlogic-gxl-cipher.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
For the whole serie you didnt use getmaintainers, so nor sunxi and amlogic maintainers where CC.
And my baylibre address which is the address for this driver.
Anyway, for this case the patch is trivial enough.
Tested-by: Corentin Labbe <clabbe@baylibre.com>
Acked-by: Corentin Labbe <clabbe@baylibre.com>
Regards
next prev parent reply other threads:[~2020-08-27 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 6:43 [PATCH v2 0/4] crypto: use kfree_sensitive() Denis Efremov
2020-08-27 6:43 ` [PATCH v2 1/4] crypto: inside-secure - " Denis Efremov
2020-08-27 14:52 ` Corentin Labbe
2020-09-02 9:02 ` Antoine Tenart
2020-09-02 13:10 ` Van Leeuwen, Pascal
2020-09-04 8:55 ` Denis Efremov
2020-09-04 9:44 ` Van Leeuwen, Pascal
2020-08-27 6:44 ` [PATCH v2 2/4] crypto: amlogic " Denis Efremov
2020-08-27 14:50 ` Corentin Labbe [this message]
2020-08-27 6:44 ` [PATCH v2 3/4] crypto: sun8i-ce " Denis Efremov
2020-08-27 14:40 ` Corentin Labbe
2020-08-27 6:44 ` [PATCH v2 4/4] crypto: sun8i-ss " Denis Efremov
2020-08-27 14:41 ` Corentin Labbe
2020-09-04 8:28 ` [PATCH v2 0/4] crypto: " Herbert Xu
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=20200827145003.GA14173@Red \
--to=clabbe.montjoie@gmail.com \
--cc=efremov@linux.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).