[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9qeM25q9S6757-fssF5114EfOEhh20A4tZmaAnPRnwM=w@mail.gmail.com>
Date: Sun, 22 Jan 2017 23:49:00 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: "Theodore Ts'o" <tytso@....edu>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Jason A. Donenfeld" <Jason@...c4.com>,
LKML <linux-kernel@...r.kernel.org>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
Andy Lutomirski <luto@...capital.net>
Subject: Re: [PATCH 1/2] random: use chacha20 for get_random_int/long
On Sun, Jan 22, 2017 at 11:28 PM, Theodore Ts'o <tytso@....edu> wrote:
> If there are other changes to the relevant lines from the networking
> tree, sure.
This patch set has *nothing* to do with the networking tree. That just
a topic confusion. There shouldn't be more discussion about
networking, because it doesn't make sense in any way at all.
> Otherwise, I was planning on taking them, since I've got
> some other changes to drivers/char/random.c I was planning on sending
> through the next merge window anyway.
Works for me. Which tree should I look for this to be queued up in?
Jason
Powered by blists - more mailing lists