All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Bestas <mkbestas@gmail.com>
To: gregkh@linuxfoundation.org
Cc: hsinyi@chromium.org, mkbestas@gmail.com, rppt@linux.ibm.com,
	stable@vger.kernel.org, swboyd@chromium.org, will@kernel.org
Subject: Re: [PATCH] arm64: map FDT as RW for early_init_dt_scan()
Date: Tue,  9 Aug 2022 21:17:53 +0300	[thread overview]
Message-ID: <20220809181753.2556152-1-mkbestas@gmail.com> (raw)
In-Reply-To: <YvKVlhUZ2I1omy5S@kroah.com>

On Tue, 9 Aug 2022 19:12:54 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:

> What about 4.14.y and newer?
> 
> thanks,
> 
> greg k-h  

This patch should be required on all stable kernels that got commit
"fdt: add support for rng-seed", however I have not tested it.

A similar backport exists in android 4.19 kernel:
https://android-review.googlesource.com/c/kernel/common/+/1238592

Without this patch, Google Pixel 3/3a fails at a very early boot
stage after merging v4.9.320+ due to the random backport.

Sorry if I messed something up with the emails, this is the first
time I submit something to a mailing list.

Thanks,

Michael Bestas

  parent reply	other threads:[~2022-08-09 18:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 14:56 [PATCH] arm64: map FDT as RW for early_init_dt_scan() Michael Bestas
2022-08-09 17:12 ` Greg KH
2022-08-09 18:11   ` Michael Bestas
2022-08-09 18:17   ` Michael Bestas [this message]
2022-08-19 11:07     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2022-08-31 20:30 Michael Bestas
2022-08-31 20:32 Michael Bestas
2022-09-01  9:57 ` Greg KH
2022-09-01 10:57   ` Michael Bestas
2022-09-01 12:07     ` Greg KH

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=20220809181753.2556152-1-mkbestas@gmail.com \
    --to=mkbestas@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsinyi@chromium.org \
    --cc=rppt@linux.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=swboyd@chromium.org \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.