public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Alexander Bergmann <abergmann@suse.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: DRBG return code handling inside testmgr.c
Date: Tue, 10 Mar 2015 17:11:44 +0100	[thread overview]
Message-ID: <4902694.okiizoKH4z@tachyon.chronox.de> (raw)
In-Reply-To: <20150310151417.GU786@surtsey.monkey.lab>

Am Dienstag, 10. März 2015, 16:14:17 schrieb Alexander Bergmann:

Hi Alexander,

> Hi Herbert,
> 
> I just fixed a small DRBG return code issue inside testmgr.c directly
> related to the RNG changes Stephan submitted.

Can you please resend it as an inline patch and copy linux-crypto too?

Also, there is a similar error in test_cprng -- may I ask you to fix that one 
too?
> 
> 
> Regards,
> Alex


-- 
Ciao
Stephan

  reply	other threads:[~2015-03-10 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 15:14 [PATCH] crypto: DRBG return code handling inside testmgr.c Alexander Bergmann
2015-03-10 16:11 ` Stephan Mueller [this message]
2015-03-10 21:48 ` 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=4902694.okiizoKH4z@tachyon.chronox.de \
    --to=smueller@chronox.de \
    --cc=abergmann@suse.com \
    --cc=herbert@gondor.apana.org.au \
    --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