[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5589E95C.2000409@roeck-us.net>
Date: Tue, 23 Jun 2015 16:18:52 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Stephan Mueller <smueller@...onox.de>,
Geert Uytterhoeven <geert@...ux-m68k.org>
CC: Herbert Xu <herbert@...dor.apana.org.au>,
Peter Zijlstra
<public-peterz-wegcikhe2lqwvfeawa7xhq@...ne.gmane.org>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Jim Davis <jim.epost@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux-Next <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
linux-crypto@...r.kernel.org, Waiman Long <waiman.long@...com>,
Ingo Molnar <mingo@...nel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH] crypto: jitterentropy - avoid compiler warnings
On 06/23/2015 10:55 AM, Stephan Mueller wrote:
> Am Dienstag, 23. Juni 2015, 10:41:03 schrieb Guenter Roeck:
>
> Hi Guenter, Geert,
>
>> 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?
>> No build failures for all architectures.
>
> Thank you very much for your help.
>
> Now, if Geert would be so kind and have a check on his OpenRISC to ensure that
> there are no compiler warnings, I would be happy.
>
> Though, does anybody have any idea what the AVR32 compiler warning about
> crypto/builtin.o not being relaxable mean and whether that is an issue? Note,
> when I was compiling AVR32, I saw some of these warnings for other builtin.o
> too.
>
At least it compiles ;-). I don't think there is anything else we can do.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists