From: Conor Dooley <conor@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>,
Conor Dooley <conor.dooley@microchip.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 6.2.11 v2 0/3] Fixes for dtb mapping
Date: Sat, 29 Apr 2023 10:56:32 +0100 [thread overview]
Message-ID: <20230429-designing-unpleased-63a3a3e59aa3@spud> (raw)
In-Reply-To: <2023042822-pushpin-coil-b0bc@gregkh>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
On Fri, Apr 28, 2023 at 01:15:35PM +0200, Greg KH wrote:
> On Fri, Apr 28, 2023 at 12:37:42PM +0200, Alexandre Ghiti wrote:
> > We used to map the dtb differently between early_pg_dir and
> > swapper_pg_dir which caused issues when we referenced addresses from
> > the early mapping with swapper_pg_dir (reserved_mem): move the dtb mapping
> > to the fixmap region in patch 1, which allows to simplify dtb handling in
> > patch 2.
> >
> > base-commit-tag: v6.2.11
>
> Thanks for redoing all of these, now queued up!
Aye, thanks for both that & for doing the fixmap stuff in the first
place Alex :)
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-04-29 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 10:37 [PATCH 6.2.11 v2 0/3] Fixes for dtb mapping Alexandre Ghiti
2023-04-28 10:37 ` [PATCH 6.2.11 v2 1/3] riscv: Move early dtb mapping into the fixmap region Alexandre Ghiti
2023-04-28 10:37 ` [PATCH 6.2.11 v2 2/3] riscv: Do not set initial_boot_params to the linear address of the dtb Alexandre Ghiti
2023-04-28 10:37 ` [PATCH 6.2.11 v2 3/3] riscv: No need to relocate the dtb as it lies in the fixmap region Alexandre Ghiti
2023-04-28 11:15 ` [PATCH 6.2.11 v2 0/3] Fixes for dtb mapping Greg KH
2023-04-29 9:56 ` Conor Dooley [this message]
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=20230429-designing-unpleased-63a3a3e59aa3@spud \
--to=conor@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=gregkh@linuxfoundation.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