From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guenter Roeck Subject: Re: [PATCH] crypto: jitterentropy - avoid compiler warnings Date: Tue, 23 Jun 2015 08:31:10 -0700 Message-ID: <20150623153110.GA10784@roeck-us.net> References: <33380936.3jDOACMRCz@tachyon.chronox.de> <1446731.BXdYRBoPhr@tachyon.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from bh-25.webhostbox.net ([208.91.199.152]:51237 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754805AbbFWPbP (ORCPT ); Tue, 23 Jun 2015 11:31:15 -0400 Content-Disposition: inline In-Reply-To: <1446731.BXdYRBoPhr@tachyon.chronox.de> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephan Mueller Cc: Geert Uytterhoeven , Herbert Xu , Peter Zijlstra , Andy Shevchenko , Jim Davis , Stephen Rothwell , Linux-Next , "linux-kernel@vger.kernel.org" , "David S. Miller" , linux-crypto@vger.kernel.org, Waiman Long , Ingo Molnar , x86 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. Guenter