From: Oreoluwa Babatunde <quic_obabatun@quicinc.com>
To: Mark Brown <broonie@kernel.org>, Nathan Chancellor <nathan@kernel.org>
Cc: <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 14:43:11 -0700 [thread overview]
Message-ID: <c8dc6827-a757-42cc-8532-314f8da37d3a@quicinc.com> (raw)
In-Reply-To: <abab36b4-e9ef-40ff-adbd-fde0f016f3b8@sirena.org.uk>
On 6/25/2024 2:25 PM, Mark Brown wrote:
>> 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.
Hi Mark,
I uploaded a fix about a week ago here:
https://lore.kernel.org/all/20240620001027.2326275-1-quic_obabatun@quicinc.com/
It is still pending review and expected to be merged if everything
is okay.
You can use this and see if it works for you. If it does, you can
also add a 'Tested-by:' tag to help speed things up.
Thank you!
Oreoluwa
next prev parent reply other threads:[~2024-06-25 21:43 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 ` [PATCH v6 1/4] of: reserved_mem: Restruture how the reserved memory regions are processed Mark Brown
2024-06-25 21:43 ` Oreoluwa Babatunde [this message]
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=c8dc6827-a757-42cc-8532-314f8da37d3a@quicinc.com \
--to=quic_obabatun@quicinc.com \
--cc=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=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®