From: Stephan Mueller <smueller@chronox.de>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: fix AEAD tag memory handling
Date: Tue, 01 Nov 2016 15:18:53 +0100 [thread overview]
Message-ID: <7741046.u5ygJjeQJs@tauon.atsec.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1610311456250.4111@mjmartin-mac01.local>
Am Montag, 31. Oktober 2016, 16:18:32 CET schrieb Mat Martineau:
Hi Mat,
> My main concern is getting the semantics correct and consistent in a
> single patch series. It would be a big problem to explain that AF_ALG AEAD
> read and write works one way in 4.x, another way in 4.y, and some
> different way in 4.z.
Ok, I will prepare another patch with this one fixed as well.
Ciao
Stephan
next prev parent reply other threads:[~2016-11-01 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 1:00 [PATCH] crypto: fix AEAD tag memory handling Stephan Mueller
2016-10-27 21:42 ` Mat Martineau
2016-10-27 22:20 ` Stephan Mueller
2016-10-28 22:21 ` Mat Martineau
2016-10-31 10:11 ` Stephan Mueller
2016-10-31 23:18 ` Mat Martineau
2016-11-01 14:18 ` Stephan Mueller [this message]
2016-11-09 13:20 ` Stephan Mueller
2016-11-10 0:26 ` Mat Martineau
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=7741046.u5ygJjeQJs@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.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