From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Subject: Re: [PATCH v25 10/12] LRNG - add TRNG support Date: Tue, 19 Nov 2019 13:41:50 +0100 Message-ID: <20191119124150.GB1975017@kroah.com> References: <5390778.VeFRgus4bQ@positron.chronox.de> <3159012.PsEOTp9LqO@positron.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Andy Lutomirski Cc: Stephan =?iso-8859-1?Q?M=FCller?= , Arnd Bergmann , Linux Crypto Mailing List , LKML , Linux API , "Eric W. Biederman" , "Alexander E. Patrakov" , "Ahmed S. Darwish" , "Theodore Y. Ts'o" , Willy Tarreau , Matthew Garrett , Vito Caputo , Andreas Dilger , Jan Kara , Ray Strode , William Jon McCann , zhangjs , Florian Weimer , Lennart Poettering , Nicolai List-Id: linux-api@vger.kernel.org On Tue, Nov 19, 2019 at 02:07:40AM -0800, Andy Lutomirski wrote: > > As this would introduce a new device file now, is there a special process that > > I need to follow or do I need to copy? Which major/minor number should I use? > > > > Looking into static const struct memdev devlist[] I see > > > > [8] = { "random", 0666, &random_fops, 0 }, > > [9] = { "urandom", 0666, &urandom_fops, 0 }, > > > > Shall a true_random be added here with [10]? > > I am not at all an expert on chardevs, but this sounds generally > reasonable. gregkh is probably the real authority here. [10] is the aio char device node, so you better not try to overlap it or bad things will happen :( thanks, greg k-h