From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
LKML <linux-kernel@vger.kernel.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH 1/2] random: use chacha20 for get_random_int/long
Date: Sun, 22 Jan 2017 16:20:04 +0100 [thread overview]
Message-ID: <20170122152004.GA21640@kroah.com> (raw)
In-Reply-To: <CAHmME9o=A_eao_+PJ669bsGwb4a-oB+i0TjO=R+E1J1qY5CttQ@mail.gmail.com>
On Sun, Jan 22, 2017 at 01:21:39PM +0100, Jason A. Donenfeld wrote:
> Hey Greg,
>
> On Sun, Jan 22, 2017 at 12:24 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Sat, Jan 21, 2017 at 03:08:12PM +0100, Jason A. Donenfeld wrote:
> >> Hi Ted,
> >>
> >> On Sat, Jan 21, 2017 at 7:24 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> >> > Oh, I see.
> >> >
> >> > So that's not how I would do things, but it's fine.
> >>
> >>
> >> Great, alright. In what tree should I look for these two commits? Or
> >> should I send it to the drivers/char maintainer (now CCd)?
> >
> > No objection from me, but as the core stuff is in the networking tree,
> > maybe it makes more sense for them to flow through there?
>
> The core stuff is not in the networking tree. This is nothing to do
> with the networking tree in any way at all. There might be some
> confusion because the initial discussions came from the siphash stuff,
> which is in the networking tree, but Ted and I choose a different
> route, going with chacha instead of siphash. So this is 0%
> network-related.
Sorry, you are correct, I am confused here.
> > Ted, any objection to that?
>
> Seems like either you pull or Ted pulls it.
Can you repost these? They are gone from my patch queue.
Ted, any objection for me to take these?
thanks,
greg k-h
next prev parent reply other threads:[~2017-01-22 15:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 18:32 [PATCH 1/2] random: use chacha20 for get_random_int/long Jason A. Donenfeld
2017-01-06 18:32 ` [PATCH 2/2] random: convert get_random_int/long into get_random_u32/u64 Jason A. Donenfeld
2017-01-18 3:49 ` [PATCH 1/2] random: use chacha20 for get_random_int/long Theodore Ts'o
2017-01-20 5:27 ` Jason A. Donenfeld
2017-01-20 14:28 ` Theodore Ts'o
2017-01-20 15:38 ` Jason A. Donenfeld
2017-01-21 0:10 ` Theodore Ts'o
2017-01-21 0:13 ` Jason A. Donenfeld
2017-01-20 15:47 ` Jason A. Donenfeld
2017-01-21 0:15 ` Theodore Ts'o
2017-01-21 0:16 ` Jason A. Donenfeld
2017-01-21 6:24 ` Theodore Ts'o
2017-01-21 14:08 ` Jason A. Donenfeld
2017-01-22 11:24 ` Greg Kroah-Hartman
2017-01-22 12:21 ` Jason A. Donenfeld
2017-01-22 15:20 ` Greg Kroah-Hartman [this message]
2017-01-22 15:34 ` Jason A. Donenfeld
2017-01-22 15:34 ` [PATCH 2/2] random: convert get_random_int/long into get_random_u32/u64 Jason A. Donenfeld
2017-01-22 22:28 ` [PATCH 1/2] random: use chacha20 for get_random_int/long Theodore Ts'o
2017-01-22 22:49 ` Jason A. Donenfeld
2017-01-23 0:33 ` Theodore Ts'o
2017-01-23 8:12 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2016-12-22 18:07 Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170122152004.GA21640@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox