From: "Stephan Müller" <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH v11 0/2] crypto: AF_ALG memory management fix
Date: Fri, 28 Jul 2017 15:53:55 +0200 [thread overview]
Message-ID: <3098923.xryRsmobXR@tauon.chronox.de> (raw)
In-Reply-To: <20170728134936.GA21401@gondor.apana.org.au>
Am Freitag, 28. Juli 2017, 15:49:36 CEST schrieb Herbert Xu:
Hi Herbert,
> All patches applied. Yes please post follow-up patches to clean
> up as necessary.
Thank you. I will do that asap.
I would add the common service code to crypto/af_alg.c or do you prefer a
separate or different file?
As the copy-AAD patch is also outstanding, in which order would you like to
receive the patches (first the code consolidation patches or first the copy-
AAD patch)?
Ciao
Stephan
next prev parent reply other threads:[~2017-07-28 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 15:12 [PATCH v11 0/2] crypto: AF_ALG memory management fix Stephan Müller
2017-06-25 15:12 ` [PATCH v11 1/2] crypto: skcipher AF_ALG - overhaul memory management Stephan Müller
2017-06-25 15:12 ` [PATCH v11 2/2] crypto: aead " Stephan Müller
2017-07-28 13:49 ` [PATCH v11 0/2] crypto: AF_ALG memory management fix Herbert Xu
2017-07-28 13:53 ` Stephan Müller [this message]
2017-07-28 13:56 ` 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=3098923.xryRsmobXR@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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