From: Rob Herring <robh@kernel.org>
To: Maxime Ripard <mripard@kernel.org>
Cc: Saravana Kannan <saravanak@google.com>,
Eric Chanudet <echanude@redhat.com>,
Radu Rendec <rrendec@redhat.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: Make the number of reserved memory regions configurable
Date: Mon, 27 Oct 2025 08:48:42 -0500 [thread overview]
Message-ID: <20251027134842.GA274032-robh@kernel.org> (raw)
In-Reply-To: <6moxms5mnvjgvfxie4zoewdvq4bbmg56hmtpohdxwujdqydxqg@r2x2rvrpjh6g>
On Mon, Oct 27, 2025 at 11:02:39AM +0100, Maxime Ripard wrote:
> Hi Rob,
>
> Thanks for your answer!
>
> On Fri, Oct 24, 2025 at 07:57:06AM -0500, Rob Herring wrote:
> > On Thu, Oct 23, 2025 at 10:35 AM Maxime Ripard <mripard@kernel.org> wrote:
> > >
> > > Some platforms register more reserved memory regions than the current
> > > hardcoded limit of 64.
> >
> > I've already NAKed a kconfig option for this before.
> >
> > The limit is now 64 dynamic regions, not total. The static regions are
> > unlimited. What platform needs so many regions and to abuse
> > /reserved-memory like this?
>
> I'm sorry, I totally missed both that you nacked it and that it got
> fixed recently. We're still seeing the issue with 6.12, but it looks like
>
> https://lore.kernel.org/all/20241008220624.551309-1-quic_obabatun@quicinc.com/
>
> Is the series you were talking about?
Yes. Plus some fixes on top of that. Every time this code is touched, we
break someone...
Rob
prev parent reply other threads:[~2025-10-27 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 15:35 Maxime Ripard
2025-10-24 12:57 ` Rob Herring
2025-10-27 10:02 ` Maxime Ripard
2025-10-27 13:48 ` Rob Herring [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=20251027134842.GA274032-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=echanude@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=rrendec@redhat.com \
--cc=saravanak@google.com \
/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®