From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-kernel@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Theodore Ts'o <tytso@mit.edu>,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: [PATCH 0/3] random: maintenance administrivia
Date: Thu, 10 Feb 2022 16:50:09 +0100 [thread overview]
Message-ID: <20220210155012.136485-1-Jason@zx2c4.com> (raw)
These patches aren't very interesting: removing unused debugging code
and switching to SPDX. I'm not aware of any special ritual being
required to SPDXify a file aside from just doing it, but please correct
me if I'm wrong; none of the copyright info changes.
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>
Jason A. Donenfeld (3):
random: remove ifdef'd out interrupt bench
random: remove unused tracepoints
random: add proper SPDX header
drivers/char/random.c | 110 +-----------------
include/linux/random.h | 5 -
include/trace/events/random.h | 206 ----------------------------------
lib/random32.c | 2 -
4 files changed, 5 insertions(+), 318 deletions(-)
delete mode 100644 include/trace/events/random.h
--
2.35.0
next reply other threads:[~2022-02-10 15:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 15:50 Jason A. Donenfeld [this message]
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
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=20220210155012.136485-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--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®