Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible

From	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Newsgroups	linux.kernel
Subject	Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible
Date	2017-07-18 10:40 +0200
Message-ID	<u4wcV-8tn-9@gated-at.bofh.it> (permalink)
References	<u4vTz-8ne-3@gated-at.bofh.it> <u4vTA-8ne-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, Jul 18, 2017 at 09:57:55AM +0200, Stephan Müller wrote:
> --- /dev/null
> +++ b/include/crypto/jitterentropy.h
> @@ -0,0 +1,80 @@
> +/*
> + * Copyright (C) 2017, Stephan Mueller <smueller@chronox.de>
> + *
> + * Redistribution and use in source and binary forms, with or without
> + * modification, are permitted provided that the following conditions
> + * are met:
> + * 1. Redistributions of source code must retain the above copyright
> + *    notice, and the entire permission notice in its entirety,
> + *    including the disclaimer of warranties.
> + * 2. Redistributions in binary form must reproduce the above copyright
> + *    notice, this list of conditions and the following disclaimer in the
> + *    documentation and/or other materials provided with the distribution.
> + * 3. The name of the author may not be used to endorse or promote
> + *    products derived from this software without specific prior
> + *    written permission.
> + *
> + * ALTERNATIVELY, this product may be distributed under the terms of
> + * the GNU General Public License, in which case the provisions of the GPL2 are
> + * required INSTEAD OF the above restrictions.  (This clause is
> + * necessary due to a potential bad interaction between the GPL and
> + * the restrictions contained in a BSD-style copyright.)
> + *
> + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
> + * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
> + * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
> + * WHICH ARE HEREBY DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR BE
> + * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
> + * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
> + * OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
> + * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
> + * LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> + * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
> + * USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
> + * DAMAGE.
> + */
> +
> +#ifndef _JITTERENTROPY_H
> +#define _JITTERENTROPY_H
> +
> +typedef	unsigned long long	__u64;
> +typedef	long long		__s64;

types.h already has these defines, don't re-typedef them again...

Thread

[RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Stephan Müller <smueller@chronox.de> - 2017-07-18 10:20 +0200
  Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-07-18 10:40 +0200
    Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Stephan Müller <smueller@chronox.de> - 2017-07-18 10:50 +0200
      Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-07-18 11:00 +0200
        Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Stephan Müller <smueller@chronox.de> - 2017-07-18 11:00 +0200
        Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Arnd Bergmann <arnd@arndb.de> - 2017-07-18 11:10 +0200
          Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Stephan Müller <smueller@chronox.de> - 2017-07-18 11:20 +0200
            Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Arnd Bergmann <arnd@arndb.de> - 2017-07-18 11:20 +0200
              Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Stephan Müller <smueller@chronox.de> - 2017-07-18 11:20 +0200

csiph-web