All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Peter Zijlstra
	<public-peterz-wegcikhe2lqwvfeawa7xhq@plane.gmane.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Jim Davis <jim.epost@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, Waiman Long <waiman.long@hp.com>,
	Ingo Molnar <mingo@kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH] crypto: jitterentropy - avoid compiler warnings
Date: Thu, 25 Jun 2015 23:37:50 +0800	[thread overview]
Message-ID: <20150625153750.GF11592@gondor.apana.org.au> (raw)
In-Reply-To: <1446731.BXdYRBoPhr@tachyon.chronox.de>

On Tue, Jun 23, 2015 at 04:18:54PM +0200, Stephan Mueller wrote:
> Hi Geert, Guenter,
> 
> may I ask that you check that the following patch compiles without errors or warnings on your systems?
> 
> Though, when I test that patch with the AVR32 cross compiler, I get a warning about the code being not relaxable.
> 
> Thank you very much.
> 
> ---8<---
> The core of the Jitter RNG is intended to be compiled with -O0. To
> ensure that the Jitter RNG can be compiled on all architectures,
> separate out the RNG core into a stand-alone C file that can be compiled
> with -O0 which does not depend on any kernel include file.
> 
> As no kernel includes can be used in the C file implementing the core
> RNG, any dependencies on kernel code must be extracted.
> 
> A second file provides the link to the kernel and the kernel crypto API
> that can be compiled with the regular compile options of the kernel.
> 
> Signed-off-by: Stephan Mueller <smueller@chronox.de>

Applied.
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  parent reply	other threads:[~2015-06-25 15:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  9:17 #pragma GCC warnings (was: Re: [PATCH] crypto: drbg - use pragmas for disabling optimization) Geert Uytterhoeven
2015-06-23  9:17 ` Geert Uytterhoeven
2015-06-23  9:21 ` Herbert Xu
2015-06-23  9:21   ` Herbert Xu
2015-06-23  9:45   ` Stephan Mueller
2015-06-23  9:45     ` Stephan Mueller
2015-06-23 13:01   ` Stephan Mueller
2015-06-23 13:01     ` Stephan Mueller
2015-06-23 13:17     ` Geert Uytterhoeven
2015-06-23 13:17       ` Geert Uytterhoeven
2015-06-23 14:18       ` [PATCH] crypto: jitterentropy - avoid compiler warnings Stephan Mueller
2015-06-23 14:18         ` Stephan Mueller
2015-06-23 15:31         ` Guenter Roeck
2015-06-23 15:31           ` Guenter Roeck
2015-06-23 15:36           ` Stephan Mueller
2015-06-23 15:36             ` Stephan Mueller
2015-06-23 17:41         ` Guenter Roeck
2015-06-23 17:41           ` Guenter Roeck
2015-06-23 17:55           ` Stephan Mueller
2015-06-23 17:55             ` Stephan Mueller
2015-06-23 23:18             ` Guenter Roeck
2015-06-23 23:18               ` Guenter Roeck
2015-06-23 18:15         ` Geert Uytterhoeven
2015-06-23 18:15           ` Geert Uytterhoeven
2015-06-25 15:37         ` Herbert Xu [this message]
2015-06-25 15: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=20150625153750.GF11592@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=andy.shevchenko@gmail.com \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=jim.epost@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mingo@kernel.org \
    --cc=public-peterz-wegcikhe2lqwvfeawa7xhq@plane.gmane.org \
    --cc=sfr@canb.auug.org.au \
    --cc=smueller@chronox.de \
    --cc=waiman.long@hp.com \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.