[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y1zkmg0l.ffs@tglx>
Date: Mon, 02 May 2022 11:37:46 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
arnd@...db.de, Theodore Ts'o <tytso@....edu>
Subject: Re: [PATCH v6 06/17] timekeeping: add raw clock fallback for
random_get_entropy()
On Mon, Apr 25 2022 at 15:22, Jason A. Donenfeld wrote:
> On Mon, Apr 25, 2022 at 02:37:11PM +0200, Thomas Gleixner wrote:
>> On Sat, Apr 23 2022 at 23:26, Jason A. Donenfeld wrote:
>> >
>> > Cc: Thomas Gleixner <tglx@...utronix.de>
>> > Cc: Arnd Bergmann <arnd@...db.de>
>> > Cc: Theodore Ts'o <tytso@....edu>
>> > Signed-off-by: Jason A. Donenfeld <Jason@...c4.com>
>>
>> Not that I care much, but in general taking over authorship w/o
>> attribution via Suggested-by or such is frowned upon.
>
> Sorry about that. Usually I'm pretty good about adding those. I guess
> something must have gotten lost this time through, as the v1 of this
> started out using sched_clock() (Arnd's suggestion) and then moved to
> using the raw ktime clock after your suggestion, and I missed the
> Suggested-by. I'll add that. Meanwhile, do you want to Ack this patch?
> Do the technical aspects look okay to you?
Yes. Please fix the subject line:
timekeeping: Add raw clock fallback for random_get_entropy()
and stick the Cc's below the SOB, so it conforms with the TIP tree
rules. Other than that:
Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
Powered by blists - more mailing lists