Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751559AbdGRIxR (ORCPT ); Tue, 18 Jul 2017 04:53:17 -0400 Received: from mail.eperm.de ([89.247.134.16]:60652 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751381AbdGRIxP (ORCPT ); Tue, 18 Jul 2017 04:53:15 -0400 From: Stephan =?ISO-8859-1?Q?M=FCller?= To: Greg Kroah-Hartman Cc: "Jason A. Donenfeld" , Arnd Bergmann , linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible Date: Tue, 18 Jul 2017 10:53:13 +0200 Message-ID: <9620599.PVNUmZQuZk@positron.chronox.de> In-Reply-To: <20170718084959.GA25267@kroah.com> References: <3910055.ntkqcq1Chb@positron.chronox.de> <5020806.nso7MErEBx@positron.chronox.de> <20170718084959.GA25267@kroah.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 544 Lines: 18 Am Dienstag, 18. Juli 2017, 10:49:59 CEST schrieb Greg Kroah-Hartman: Hi Greg, > > > This issue was discussed during the inclusion of the Jitter RNG C code > > into > > the kernel. > > Ok, that was then, this is now, why not change it now? How does > including types.h change anything? At the time of discussion, I had no issue compiling it with types.h, but on other architectures, there were some issues. Allow me to check back with the developer who notified me about this issue to see whether types.h can be included. Ciao Stephan