Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Olivia Mackall <olivia@selenic.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, Frank Li <Frank.Li@nxp.com>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH v4 2/2] m68k: coldfire: Add RNG support for MCF54418
Date: Mon, 12 Oct 2026 01:28:24 +1000	[thread overview]
Message-ID: <8be9c875-68a9-4bb5-b581-501a0a6819f4@linux-m68k.org> (raw)
In-Reply-To: <asn8e5puc3I01Lva@gondor.apana.org.au>

Hi JM,

On 10/10/26 18:51, Herbert Xu wrote:
> On Wed, Aug 19, 2026 at 07:36:36AM +1000, Greg Ungerer wrote:
>> Hi JM,
>>
>> On 19/8/26 01:09, Jean-Michel Hautbois wrote:
>>> Hi Greg,
>>>
>>> Sorry for the very long silence on this one, it fell off my radar...
>>>
>>> Le 03/12/2025 à 13:15, Greg Ungerer a écrit :
>>>> Hi Jean-Michel,
>>>>
>>>> On 26/11/25 17:08, Jean-Michel Hautbois via B4 Relay wrote:
>>>>> From: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
>>>>>
>>>>> Add support for the hardware Random Number Generator (RNGB) found on
>>>>> MCF54418 ColdFire processors with clock enabled at platform
>>>>> initialization.
>>>>>
>>>>> The RNGB block is compatible with the imx-rngc driver.
>>>>>
>>>>> Reviewed-by: Frank Li <Frank.Li@nxp.com>
>>>>> Signed-off-by: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
>>>>> ---
>>>>>   arch/m68k/coldfire/device.c       | 28 ++++++++++++++++++++++++++++
>>>>>   arch/m68k/coldfire/m5441x.c       |  2 +-
>>>>>   arch/m68k/include/asm/m5441xsim.h |  9 +++++++++
>>>>>   drivers/char/hw_random/Kconfig    |  3 ++-
>>>>>   drivers/char/hw_random/imx-rngc.c |  7 +++++++
>>>>>   5 files changed, 47 insertions(+), 2 deletions(-)
>>>>
>>>> I am happy with the ColdFire arch parts, so from me:
>>>>
>>>>      Acked-by: Greg Ungerer <gerg@linux-m68k.org>
>>>>
>>>> I don't mind taking this commit via the m68knommu git tree if the hw_rng
>>>> maintainers are ok with that. Otherwise if you break out the arch/m68k
>>>> parts I can apply those on their own.
>>>
>>> I think Herbert acked ?
>>> Do you need another ack ?
>>
>> I would like to see an acknowledgement that taking this patch via the
>> m68knommu git tree (to Linus) is ok with the RNG maintainers.
> 
> I have no objections to this.

Thanks Herbert.

JM: I have applied this to the for-next branch of the m68knommu git tree.
I didn't quite go on cleanly, so please double check it for me.

Regards
Greg


  reply	other threads:[~2026-10-11 15:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  7:08 [PATCH v4 0/2] m68k: coldfire: Add RNG support for MCF54418 Jean-Michel Hautbois via B4 Relay
2025-11-26  7:08 ` [PATCH v4 1/2] hwrng: imx-rngc: Use optional clock Jean-Michel Hautbois via B4 Relay
2025-11-26 20:30   ` Martin Kaiser
2025-11-27  8:37     ` Geert Uytterhoeven
2025-11-27 13:22       ` Martin Kaiser
2025-12-19  3:35   ` Herbert Xu
2025-11-26  7:08 ` [PATCH v4 2/2] m68k: coldfire: Add RNG support for MCF54418 Jean-Michel Hautbois via B4 Relay
2025-12-03 12:15   ` Greg Ungerer
2026-08-18 15:09     ` Jean-Michel Hautbois
2026-08-18 21:36       ` Greg Ungerer
2026-10-10  8:51         ` Herbert Xu
2026-10-11 15:28           ` Greg Ungerer [this message]
2025-12-19  3:35   ` Herbert Xu

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=8be9c875-68a9-4bb5-b581-501a0a6819f4@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=Frank.Li@nxp.com \
    --cc=festevam@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=imx@lists.linux.dev \
    --cc=jeanmichel.hautbois@yoseli.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=olivia@selenic.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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