From: Eric Biggers <ebiggers@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: [PATCH 1/3] random: remove ifdef'd out interrupt bench
Date: Sun, 20 Feb 2022 21:18:45 -0800 [thread overview]
Message-ID: <YhMgtVaw3OjJ/u2w@sol.localdomain> (raw)
In-Reply-To: <YhMUkwfdI/GbxCT2@sol.localdomain>
On Sun, Feb 20, 2022 at 08:27:00PM -0800, Eric Biggers wrote:
> On Thu, Feb 10, 2022 at 04:50:10PM +0100, Jason A. Donenfeld wrote:
> > With tools like kbench9000 giving more finegrained responses, and this
> > basically never having been used ever since it was initially added,
> > let's just get rid of this. There *is* still work to be done on the
> > interrupt handler, but this really isn't the way it's being developed.
> >
> > Cc: Theodore Ts'o <tytso@mit.edu>
> > Cc: Dominik Brodowski <linux@dominikbrodowski.net>
> > Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> > ---
> > drivers/char/random.c | 40 ----------------------------------------
> > 1 file changed, 40 deletions(-)
>
> Reviewed-by: Eric Biggers <ebiggers@google.com>
>
> - Eric
Actually one comment: there is a reference to ADD_INTERRUPT_BENCH in
Documentation/admin-guide/sysctl/kernel.rst that needs to be removed.
- Eric
next prev parent reply other threads:[~2022-02-21 5:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 15:50 [PATCH 0/3] random: maintenance administrivia Jason A. Donenfeld
2022-02-10 15:50 ` [PATCH 1/3] random: remove ifdef'd out interrupt bench Jason A. Donenfeld
2022-02-10 16:43 ` Dominik Brodowski
2022-02-21 4:26 ` Eric Biggers
2022-02-21 5:18 ` Eric Biggers [this message]
2022-02-21 15:42 ` Jason A. Donenfeld
2022-02-21 15:44 ` [PATCH v2] " Jason A. Donenfeld
2022-02-10 15:50 ` [PATCH 2/3] random: remove unused tracepoints Jason A. Donenfeld
2022-02-10 16:43 ` Dominik Brodowski
2022-02-21 4:28 ` Eric Biggers
2022-02-10 15:50 ` [PATCH 3/3] random: add proper SPDX header Jason A. Donenfeld
2022-02-10 16:10 ` Jason A. Donenfeld
2022-02-10 16:16 ` [PATCH v2] " Jason A. Donenfeld
2022-02-10 16:49 ` Greg Kroah-Hartman
2022-02-10 16:53 ` Jason A. Donenfeld
2022-02-10 17:00 ` Greg Kroah-Hartman
2022-02-10 17:01 ` Jason A. Donenfeld
2022-02-10 17:06 ` [PATCH v3] " Jason A. Donenfeld
2022-02-10 17:12 ` Greg Kroah-Hartman
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=YhMgtVaw3OjJ/u2w@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.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
all inboxes | Powered by JetHome®