From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Bestas <mkbestas@gmail.com>
Cc: stable@vger.kernel.org, Hsin-Yi Wang <hsinyi@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
Mike Rapoport <rppt@linux.ibm.com>, Will Deacon <will@kernel.org>
Subject: Re: [PATCH] arm64: map FDT as RW for early_init_dt_scan()
Date: Thu, 1 Sep 2022 11:57:55 +0200 [thread overview]
Message-ID: <YxCCI2c6l8OdA4GV@kroah.com> (raw)
In-Reply-To: <20220831203200.1684696-1-mkbestas@gmail.com>
On Wed, Aug 31, 2022 at 11:32:00PM +0300, Michael Bestas wrote:
> From: Hsin-Yi Wang <hsinyi@chromium.org>
>
> commit e112b032a72c78f15d0c803c5dc6be444c2e6c66 upstream.
>
> Currently in arm64, FDT is mapped to RO before it's passed to
> early_init_dt_scan(). However, there might be some codes
> (eg. commit "fdt: add support for rng-seed") that need to modify FDT
> during init. Map FDT to RO after early fixups are done.
>
> Cc: stable@vger.kernel.org # 4.14
> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
> Signed-off-by: Will Deacon <will@kernel.org>
> [mkbestas: fixed trivial conflicts for 4.14 backport]
> Signed-off-by: Michael Bestas <mkbestas@gmail.com>
> ---
> arch/arm64/include/asm/mmu.h | 2 +-
> arch/arm64/kernel/kaslr.c | 5 +----
> arch/arm64/kernel/setup.c | 9 ++++++++-
> arch/arm64/mm/mmu.c | 15 +--------------
> 4 files changed, 11 insertions(+), 20 deletions(-)
>
Both now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2022-09-01 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 20:32 [PATCH] arm64: map FDT as RW for early_init_dt_scan() Michael Bestas
2022-09-01 9:57 ` Greg KH [this message]
2022-09-01 10:57 ` Michael Bestas
2022-09-01 12:07 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-08-31 20:30 Michael Bestas
2022-08-09 14:56 Michael Bestas
2022-08-09 17:12 ` Greg KH
2022-08-09 18:11 ` Michael Bestas
2022-08-09 18:17 ` Michael Bestas
2022-08-19 11: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=YxCCI2c6l8OdA4GV@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hsinyi@chromium.org \
--cc=mkbestas@gmail.com \
--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.