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 2/3] random: remove unused tracepoints
Date: Sun, 20 Feb 2022 20:28:58 -0800 [thread overview]
Message-ID: <YhMVCgUCWK7eeQE8@sol.localdomain> (raw)
In-Reply-To: <20220210155012.136485-3-Jason@zx2c4.com>
On Thu, Feb 10, 2022 at 04:50:11PM +0100, Jason A. Donenfeld wrote:
> These explicit tracepoints aren't really used and show sign of aging.
> It's work to keep these up to date, and before I attempted to keep them
> up to date, they weren't up to date, which indicates that they're not
> really used. These days there are better ways of introspecting anyway.
>
> 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 | 30 +----
> include/trace/events/random.h | 206 ----------------------------------
> lib/random32.c | 2 -
> 3 files changed, 3 insertions(+), 235 deletions(-)
> delete mode 100644 include/trace/events/random.h
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
next prev parent reply other threads:[~2022-02-21 4:29 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
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 [this message]
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=YhMVCgUCWK7eeQE8@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