public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8•de>
To: "Jason A. Donenfeld" <Jason@zx2c4•com>
Cc: linux-s390@vger•kernel.org, Arnd Bergmann <arnd@arndb•de>,
	Will Deacon <will@kernel•org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
	Catalin Marinas <catalin.marinas@arm•com>,
	Heiko Carstens <hca@linux•ibm.com>,
	x86@kernel•org, linux-kernel@vger•kernel.org,
	"H. Peter Anvin" <hpa@zytor•com>,
	Alexander Gordeev <agordeev@linux•ibm.com>,
	linuxppc-dev@lists•ozlabs.org,
	Thomas Gleixner <tglx@linutronix•de>,
	linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v3] random: remove CONFIG_ARCH_RANDOM
Date: Wed, 6 Jul 2022 14:35:17 +0200	[thread overview]
Message-ID: <YsWBhaZT5dCQHfwp@zn.tnic> (raw)
In-Reply-To: <20220706105411.406259-1-Jason@zx2c4.com>

On Wed, Jul 06, 2022 at 12:54:11PM +0200, Jason A. Donenfeld wrote:
> So this commit simplifies things by removing CONFIG_ARCH_RANDOM, keeping

No need to say "this commit" or "this patch" - just write "as if you are
giving orders to the codebase to change its behaviour."

In this case, "So simplify things by ... "

>  arch/x86/Kconfig                                  |  9 ---------
>  arch/x86/include/asm/archrandom.h                 | 14 +++++---------
>  arch/x86/kernel/cpu/rdrand.c                      |  2 --

For those:

Acked-by: Borislav Petkov <bp@suse•de>

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2022-07-06 12:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 19:01 [PATCH] random: remove CONFIG_ARCH_RANDOM and "nordrand" Jason A. Donenfeld
2022-07-05 19:36 ` Borislav Petkov
2022-07-05 19:44   ` Jason A. Donenfeld
2022-07-05 19:57     ` Borislav Petkov
2022-07-05 21:50       ` H. Peter Anvin
2022-07-05 22:00         ` Borislav Petkov
2022-07-05 23:11           ` H. Peter Anvin
2022-07-06 12:23             ` Borislav Petkov
2022-07-06 16:42               ` H. Peter Anvin
2022-07-06  0:28         ` Jason A. Donenfeld
2022-07-06  0:32           ` [PATCH v2] random: remove CONFIG_ARCH_RANDOM Jason A. Donenfeld
2022-07-06  6:41             ` Greg Kroah-Hartman
2022-07-06  8:40             ` Heiko Carstens
2022-07-06 10:54             ` [PATCH v3] " Jason A. Donenfeld
2022-07-06 12:35               ` Borislav Petkov [this message]
2022-07-06 13:55                 ` Jason A. Donenfeld
2022-07-06 14:35                   ` [PATCH v4] " Jason A. Donenfeld
2022-07-08  0:40                     ` [PATCH v5] " Jason A. Donenfeld
2022-07-13 15:46                       ` Catalin Marinas
2022-07-18 12:53                       ` Michael Ellerman
2022-08-12 13:50                       ` Geert Uytterhoeven
2022-07-06 12:30           ` [PATCH] random: remove CONFIG_ARCH_RANDOM and "nordrand" Borislav Petkov
2022-07-06 14:55 ` Theodore Ts'o
2022-07-06 15:24   ` 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=YsWBhaZT5dCQHfwp@zn.tnic \
    --to=bp@alien8$(echo .)de \
    --cc=Jason@zx2c4$(echo .)com \
    --cc=agordeev@linux$(echo .)ibm.com \
    --cc=arnd@arndb$(echo .)de \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=hca@linux$(echo .)ibm.com \
    --cc=hpa@zytor$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-s390@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=tglx@linutronix$(echo .)de \
    --cc=will@kernel$(echo .)org \
    --cc=x86@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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