From: Mark Brown <broonie@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Oreoluwa Babatunde <quic_obabatun@quicinc.com>,
robh@kernel.org, saravanak@google.com, hch@lst.de,
m.szyprowski@samsung.com, robin.murphy@arm.com, will@kernel.org,
catalin.marinas@arm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
kernel@quicinc.com
Subject: Re: [PATCH v6 1/4] of: reserved_mem: Restruture how the reserved memory regions are processed
Date: Tue, 25 Jun 2024 22:25:48 +0100 [thread overview]
Message-ID: <abab36b4-e9ef-40ff-adbd-fde0f016f3b8@sirena.org.uk> (raw)
In-Reply-To: <Zmd0Zg7oMneJLyHd@finisterre.sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On Mon, Jun 10, 2024 at 10:47:18PM +0100, Mark Brown wrote:
> On Mon, Jun 10, 2024 at 02:34:03PM -0700, Nathan Chancellor wrote:
> > On Tue, May 28, 2024 at 03:36:47PM -0700, Oreoluwa Babatunde wrote:
>
> > > fdt_init_reserved_mem() is also now called from within the
> > > unflatten_device_tree() function so that this step happens after the
> > > page tables have been setup.
>
> > > Signed-off-by: Oreoluwa Babatunde <quic_obabatun@quicinc.com>
>
> > I am seeing a warning when booting aspeed_g5_defconfig in QEMU that I
> > bisected to this change in -next as commit a46cccb0ee2d ("of:
> > reserved_mem: Restruture how the reserved memory regions are
> > processed").
>
> I'm also seeing issues in -next which I bisected to this commit, on the
> original Raspberry Pi the cpufreq driver fails to come up and I see
> (potentially separate?) backtraces:
This is still in -next and breaking boot as reported above.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-06-25 21:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 22:36 [PATCH v6 0/4] Dynamic Allocation of the reserved_mem array Oreoluwa Babatunde
2024-05-28 22:36 ` [PATCH v6 1/4] of: reserved_mem: Restruture how the reserved memory regions are processed Oreoluwa Babatunde
2024-06-10 21:34 ` Nathan Chancellor
2024-06-10 21:47 ` Mark Brown
2024-06-13 16:05 ` Oreoluwa Babatunde
2024-06-13 16:17 ` Conor Dooley
2024-06-13 16:38 ` Robin Murphy
2024-06-17 19:33 ` [PATCH] of: reserved_mem: Restructure code to call reserved mem init functions earlier Oreoluwa Babatunde
2024-06-18 8:53 ` kernel test robot
2024-06-20 0:10 ` [PATCH v2] " Oreoluwa Babatunde
2024-06-26 15:04 ` Nathan Chancellor
2024-06-26 15:16 ` Rob Herring
2024-06-26 15:48 ` Oreoluwa Babatunde
2024-06-25 21:25 ` Mark Brown [this message]
2024-06-25 21:43 ` [PATCH v6 1/4] of: reserved_mem: Restruture how the reserved memory regions are processed Oreoluwa Babatunde
2024-05-28 22:36 ` [PATCH v6 2/4] of: reserved_mem: Add code to dynamically allocate reserved_mem array Oreoluwa Babatunde
2024-05-28 22:36 ` [PATCH v6 3/4] of: reserved_mem: Use unflatten_devicetree APIs to scan reserved memory nodes Oreoluwa Babatunde
2024-07-05 13:05 ` Klara Modin
2024-07-05 15:38 ` Klara Modin
2024-07-08 23:12 ` Oreoluwa Babatunde
2024-07-08 23:45 ` Rob Herring
2024-05-28 22:36 ` [PATCH v6 4/4] of: reserved_mem: Rename fdt_* functions to refelct the change from using fdt APIs Oreoluwa Babatunde
2024-06-06 15:33 ` [PATCH v6 0/4] Dynamic Allocation of the reserved_mem array Rob Herring
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=abab36b4-e9ef-40ff-adbd-fde0f016f3b8@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=kernel@quicinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=nathan@kernel.org \
--cc=quic_obabatun@quicinc.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=saravanak@google.com \
--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 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®