From: "Stephan Müller" <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 0/2] crypto: AF_ALG memory management fix
Date: Thu, 16 Feb 2017 13:55:55 +0100 [thread overview]
Message-ID: <1562177.Y0EmCeTO2L@tauon.atsec.com> (raw)
In-Reply-To: <20170216121021.GA18940@gondor.apana.org.au>
Am Donnerstag, 16. Februar 2017, 20:10:21 CET schrieb Herbert Xu:
Hi Herbert,
> On Wed, Feb 15, 2017 at 09:47:19AM +0100, Stephan Müller wrote:
> > as I just saw that you marked my patch with changes requested in
> > patchwork,
> > may I ask which changes should be applied?
>
> I thought we agreed that we would not do the TX offset thing and
> keep the existing semantics of consuming all TX data given an RX
> request.
Ok, will do.
Ciao
Stephan
prev parent reply other threads:[~2017-02-16 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 10:04 [PATCH v3 0/2] crypto: AF_ALG memory management fix Stephan Müller
2017-02-13 10:05 ` [PATCH v3 1/2] crypto: skcipher AF_ALG - overhaul memory management Stephan Müller
2017-02-13 10:05 ` [PATCH v3 2/2] crypto: aead " Stephan Müller
2017-02-15 8:47 ` [PATCH v3 0/2] crypto: AF_ALG memory management fix Stephan Müller
2017-02-16 12:10 ` Herbert Xu
2017-02-16 12:55 ` Stephan Müller [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=1562177.Y0EmCeTO2L@tauon.atsec.com \
--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;
as well as URLs for NNTP newsgroup(s).