From: Markus Elfring <Markus.Elfring@web.de>
To: Gilad Ben-Yossef <gilad@benyossef.com>, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
Ofir Drang <ofir.drang@arm.com>
Subject: Re: [PATCH v2 1/3] crypto: ccree: fix resource leak on error path
Date: Sun, 21 Jun 2020 15:07:16 +0200 [thread overview]
Message-ID: <2857f54e-e752-0555-f43a-a451f64f6302@web.de> (raw)
In-Reply-To: <20200621112000.31495-2-gilad@benyossef.com>
> Fix a small resource leak on the error path of cipher processing.
I find it more appropriate to resend this patch series with a cover letter
together with all update steps.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=64677779e8962c20b580b471790fe42367750599#n785
Where would you like to put the patch version descriptions?
Regards,
Markus
next prev parent reply other threads:[~2020-06-21 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 11:19 [PATCH v2 0/3] fixes and update to essiv support Gilad Ben-Yossef
2020-06-21 11:19 ` [PATCH v2 1/3] crypto: ccree: fix resource leak on error path Gilad Ben-Yossef
2020-06-21 13:07 ` Markus Elfring [this message]
2020-06-21 13:21 ` Gilad Ben-Yossef
2020-06-21 13:35 ` Markus Elfring
2020-06-21 11:19 ` [PATCH v2 2/3] crypto: ccree: adapt ccree essiv support to kcapi Gilad Ben-Yossef
2020-06-21 13:15 ` Markus Elfring
2020-06-21 11:19 ` [PATCH v2 3/3] crypto: ccree: remove unused field Gilad Ben-Yossef
2020-06-26 6:09 ` [PATCH v2 0/3] fixes and update to essiv support 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=2857f54e-e752-0555-f43a-a451f64f6302@web.de \
--to=markus.elfring@web.de \
--cc=davem@davemloft.net \
--cc=gilad@benyossef.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ofir.drang@arm.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;
as well as URLs for NNTP newsgroup(s).