From: Greg KH <greg@kroah.com>
To: Jeff Liu <jeff.liu@oracle.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 06/24] crypt: return actual error code on pcrypt_init
Date: Tue, 17 Jun 2014 12:24:48 -0700 [thread overview]
Message-ID: <20140617192448.GD4628@kroah.com> (raw)
In-Reply-To: <53A050AE.2050401@oracle.com>
On Tue, Jun 17, 2014 at 10:29:02PM +0800, Jeff Liu wrote:
> From: Jie Liu <jeff.liu@oracle.com>
>
> Return the actual error code if call kset_create_and_add() failed
>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: David S. Miller" <davem@davemloft.net>
> Signed-off-by: Jie Liu <jeff.liu@oracle.com>
> ---
> crypto/pcrypt.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Herbert and David, please do not take this patch, it is incorrect.
thanks,
greg k-h
prev parent reply other threads:[~2014-06-17 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 14:29 [PATCH 06/24] crypt: return actual error code on pcrypt_init Jeff Liu
2014-06-17 19:24 ` Greg KH [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=20140617192448.GD4628@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jeff.liu@oracle.com \
--cc=linux-crypto@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).