linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-abi@vger.kernel.org, linux-crypto@vger.kernel.org,
	beck@openbsd.org, deraadt@cvs.openbsd.org
Subject: Re: [PATCH, RFC -v3] random: introduce getrandom(2) system call
Date: Fri, 18 Jul 2014 07:51:22 -0400	[thread overview]
Message-ID: <20140718115122.GG1491@thunk.org> (raw)
In-Reply-To: <CAFLxGvy7CwWiagxMHixHnuUwvimBOOJyJqs4g2Rq8hzoUA60mw@mail.gmail.com>

On Fri, Jul 18, 2014 at 12:25:17PM +0200, Richard Weinberger wrote:
> >                     if (ret != buflen)
> 
> A small nit-pick, missing "{".

Thanks, good catch.   Fixed.

						- Ted

      reply	other threads:[~2014-07-18 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18  9:59 [PATCH, RFC -v3] random: introduce getrandom(2) system call Theodore Ts'o
2014-07-18 10:25 ` Richard Weinberger
2014-07-18 11:51   ` Theodore Ts'o [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=20140718115122.GG1491@thunk.org \
    --to=tytso@mit.edu \
    --cc=beck@openbsd.org \
    --cc=deraadt@cvs.openbsd.org \
    --cc=linux-abi@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.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).