From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933102AbbFWXTG (ORCPT ); Tue, 23 Jun 2015 19:19:06 -0400 Received: from bh-25.webhostbox.net ([208.91.199.152]:53281 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751259AbbFWXS6 (ORCPT ); Tue, 23 Jun 2015 19:18:58 -0400 Message-ID: <5589E95C.2000409@roeck-us.net> Date: Tue, 23 Jun 2015 16:18:52 -0700 From: Guenter Roeck User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Stephan Mueller , Geert Uytterhoeven CC: 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 Subject: Re: [PATCH] crypto: jitterentropy - avoid compiler warnings References: <1446731.BXdYRBoPhr@tachyon.chronox.de> <20150623174103.GA11973@roeck-us.net> <1763021.bXoJhbvnM9@tauon.atsec.com> In-Reply-To: <1763021.bXoJhbvnM9@tauon.atsec.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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