From: Gilad Ben-Yossef Subject: Re: [PATCH v5 05/19] crypto: introduce crypto wait for async op Date: Mon, 21 Aug 2017 15:49:41 +0300 Message-ID: References: <1502724094-23305-1-git-send-email-gilad@benyossef.com> <1502724094-23305-6-git-send-email-gilad@benyossef.com> <20170815032303.000042b2@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: Herbert Xu , "David S. Miller" , Jonathan Corbet , David Howells , Tom Lendacky , Gary Hook , Boris Brezillon , Arnaud Ebalard , Matthias Brugger , Alasdair Kergon , Mike Snitzer , device-mapper development , Shaohua Li , Steve French , "Theodore Y. Ts'o" , Jaegeuk Kim , Mimi Zohar , Dmitry Kasatkin , James Morris , "Serge E. Hallyn To: Jonathan Cameron Return-path: In-Reply-To: <20170815032303.000042b2@huawei.com> Sender: owner-linux-security-module@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Tue, Aug 15, 2017 at 5:23 AM, Jonathan Cameron wrote: > On Mon, 14 Aug 2017 18:21:15 +0300 > Gilad Ben-Yossef wrote: > >> Invoking a possibly async. crypto op and waiting for completion >> while correctly handling backlog processing is a common task >> in the crypto API implementation and outside users of it. >> >> This patch adds a generic implementation for doing so in >> preparation for using it across the board instead of hand >> rolled versions. > > Trivial observation. Shouldn't have this bonus blank line inserted here. > >> #endif /* _LINUX_CRYPTO_H */ >> > Indeed. Will be fixed. Thanks, Gilad -- Gilad Ben-Yossef Chief Coffee Drinker "If you take a class in large-scale robotics, can you end up in a situation where the homework eats your dog?" -- Jean-Baptiste Queru