From: Stephan Mueller <smueller@chronox.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
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: Tue, 23 Jun 2015 17:36:56 +0200 [thread overview]
Message-ID: <2463718.ZGeM8ImuD9@tauon.atsec.com> (raw)
In-Reply-To: <20150623153110.GA10784@roeck-us.net>
Am Dienstag, 23. Juni 2015, 08:31:10 schrieb Guenter Roeck:
Hi Guenter,
>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?
>Stephan,
>
>I applied your patch on top of the current mainline (which includes
>the crypto updates for 4.2) and pushed it into my 'testing' branch.
>You should be able to see the results in a couple of hours at
>http://server.roeck-us.net:8010/builders, in the 'testing' column.
>
>The build system doesn't log warnings, but this should give us an idea
>if the build passes for all architectures.
>
>I'll have a look myself later and let you know as well.
Thank you very much!
Ciao
Stephan
next prev parent reply other threads:[~2015-06-23 15:37 UTC|newest]
Thread overview: 13+ 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:21 ` Herbert Xu
2015-06-23 9:45 ` Stephan Mueller
2015-06-23 13:01 ` Stephan Mueller
2015-06-23 13:17 ` Geert Uytterhoeven
2015-06-23 14:18 ` [PATCH] crypto: jitterentropy - avoid compiler warnings Stephan Mueller
2015-06-23 15:31 ` Guenter Roeck
2015-06-23 15:36 ` Stephan Mueller [this message]
2015-06-23 17:41 ` Guenter Roeck
2015-06-23 17:55 ` Stephan Mueller
2015-06-23 23:18 ` Guenter Roeck
2015-06-23 18:15 ` Geert Uytterhoeven
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=2463718.ZGeM8ImuD9@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--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=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.