From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] powerpc/rng: wire up during setup_arch
Date: Sat, 11 Jun 2022 10:41:52 +0000 [thread overview]
Message-ID: <230d6927-b11a-fbf2-fb1c-fa9df70acfa0@csgroup.eu> (raw)
In-Reply-To: <YqRnPzVxK9HKROYi@zx2c4.com>
Le 11/06/2022 à 11:58, Jason A. Donenfeld a écrit :
> Hi Christophe,
>
> On Sat, Jun 11, 2022 at 09:27:43AM +0000, Christophe Leroy wrote:
>> Le 11/06/2022 à 11:22, Jason A. Donenfeld a écrit :
>>> Hi Christophe,
>>>
>>> On Sat, Jun 11, 2022 at 11:17:23AM +0200, Christophe Leroy wrote:
>>>> Also, you copied stable. Should you add a Fixes: tag so that we know
>>>> what it fixes ?
>>>
>>> I suppose the fixes tag would be whatever introduced those files in the
>>> first place, so not all together useful. But if you want something, feel
>>> free to append these when applying the commit:
>>>
>>> Fixes: a4da0d50b2a0 ("powerpc: Implement arch_get_random_long/int() for powernv")
>>> Fixes: a489043f4626 ("powerpc/pseries: Implement arch_get_random_long() based on H_RANDOM")
>>> Fixes: c25769fddaec ("powerpc/microwatt: Add support for hardware random number generator")
>>>
>>
>> Well it helps knowing on which stable version it applies.
>>
>> Maybe it would be cleaner to send three patches ? After all they look
>
> Sounds like irritating paperwork to me.
It helps with application to stable.
Two of the above commits are in v3.12, the other one appears in v5.13
So having the microwatt in a separate patch should ease.
>
>> like 3 independant changes with nothing in common at all.
>
> "Nothing in common"? I don't know about that.
I mean no common file that needs to be changed for the three platforms,
so it makes it easy.
>
> Anyway, sure, I'll do that and send a v2 series.
>
As they are independant it doesn't need to be a series at all. But
that's fine if it is a series as well.
Christophe
next prev parent reply other threads:[~2022-06-11 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 8:11 Jason A. Donenfeld
2022-06-11 9:16 ` Christophe Leroy
2022-06-11 9:17 ` Christophe Leroy
2022-06-11 9:22 ` Jason A. Donenfeld
2022-06-11 9:27 ` Christophe Leroy
2022-06-11 9:58 ` Jason A. Donenfeld
2022-06-11 10:06 ` Jason A. Donenfeld
2022-06-11 10:41 ` Christophe Leroy [this message]
2022-06-11 9:20 ` Jason A. Donenfeld
2022-06-11 9:23 ` Christophe Leroy
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=230d6927-b11a-fbf2-fb1c-fa9df70acfa0@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@vger.kernel.org \
/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®