From: Alexander Alemayhu <alexander@alemayhu.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
davem@davemloft.net, netdev@vger.kernel.org, ofir.drang@arm.com,
gilad.benyossef@arm.com
Subject: Re: [PATCH net-next] IPsec: do not ignore crypto err in ah input
Date: Fri, 13 Jan 2017 08:45:51 +0100 [thread overview]
Message-ID: <20170113074551.GA24287@gmail.com> (raw)
In-Reply-To: <1484228002-25078-1-git-send-email-gilad@benyossef.com>
On Thu, Jan 12, 2017 at 03:33:22PM +0200, Gilad Ben-Yossef wrote:
> ah input processing uses the asynchrnous hash crypto API which
> supplies an error code as part of the operation completion but
> the error code was being ignored.
>
s/asynchrnous/asynchronous
--
Mit freundlichen Grüßen
Alexander Alemayhu
next prev parent reply other threads:[~2017-01-13 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 13:33 [PATCH net-next] IPsec: do not ignore crypto err in ah input Gilad Ben-Yossef
2017-01-13 7:45 ` Alexander Alemayhu [this message]
2017-01-15 6:06 ` Gilad Ben-Yossef
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=20170113074551.GA24287@gmail.com \
--to=alexander@alemayhu.com \
--cc=davem@davemloft.net \
--cc=gilad.benyossef@arm.com \
--cc=gilad@benyossef.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=ofir.drang@arm.com \
--cc=steffen.klassert@secunet.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).