From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
davem@davemloft.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: document correct return value for request allocation
Date: Mon, 4 Apr 2016 09:27:22 +0200 [thread overview]
Message-ID: <20160404072722.GA856@Red> (raw)
In-Reply-To: <1459612496-5094-1-git-send-email-ebiggers3@gmail.com>
On Sat, Apr 02, 2016 at 10:54:56AM -0500, Eric Biggers wrote:
> Signed-off-by: Eric Biggers <ebiggers3@gmail.com>
> ---
> Documentation/DocBook/crypto-API.tmpl | 6 +++---
> include/crypto/aead.h | 3 +--
> include/crypto/hash.h | 3 +--
> include/crypto/skcipher.h | 3 +--
> include/linux/crypto.h | 3 +--
> 5 files changed, 7 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/DocBook/crypto-API.tmpl b/Documentation/DocBook/crypto-API.tmpl
> index 348619f..d55dc5a 100644
> --- a/Documentation/DocBook/crypto-API.tmpl
> +++ b/Documentation/DocBook/crypto-API.tmpl
> @@ -1936,9 +1936,9 @@ static int test_skcipher(void)
> }
>
> req = skcipher_request_alloc(skcipher, GFP_KERNEL);
> - if (IS_ERR(req)) {
> - pr_info("could not allocate request queue\n");
> - ret = PTR_ERR(req);
> + if (!req) {
> + pr_info("could not allocate skcipher request\n");
> + ret = -ENOMEM;
> goto out;
> }
Hello
I think pr_err is better than pr_info.
Regards
next prev parent reply other threads:[~2016-04-04 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 15:54 [PATCH] crypto: document correct return value for request allocation Eric Biggers
2016-04-04 7:27 ` LABBE Corentin [this message]
2016-04-15 14:37 ` 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=20160404072722.GA856@Red \
--to=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=ebiggers3@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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).