From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: Stewart Smith <stewart@linux.vnet.ibm.com>,
Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org, obh+dt@kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] drivers: of: increase MAX_RESERVED_REGIONS to 32
Date: Mon, 2 Oct 2017 19:58:30 -0300 [thread overview]
Message-ID: <ddd472b4-6eea-80a3-53c6-bd63b565ff63@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170926084000.29105-1-stewart@linux.vnet.ibm.com>
On 09/26/2017 05:40 AM, Stewart Smith wrote:
> The simple fix is to bump the length of the array to 32 which "should be
> enough for everyone(TM)".
Tested-by: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
# uname -r
4.14.0-rc3
# dmesg
[ 0.000000] opal: OPAL detected !
[ 0.000000] crashkernel: memory value expected
[ 0.000000] OF: reserved mem: not enough space all defined regions.
[ 0.000000] OF: reserved mem: not enough space all defined regions.
[ 0.000000] OF: reserved mem: not enough space all defined regions.
[ 0.000000] OF: reserved mem: not enough space all defined regions.
[ 0.000000] Allocated 2883584 bytes for 2048 pacas at c00000000fd40000
<...>
# uname -r
4.14.0-rc3.of32maxrsvdmemregions
# dmesg | head
[ 0.000000] opal: OPAL detected !
[ 0.000000] crashkernel: memory value expected
[ 0.000000] Allocated 2883584 bytes for 2048 pacas at c00000000fd40000
<...>
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
next prev parent reply other threads:[~2017-10-02 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 10:24 [PATCH] drivers: of: static DT reservations incorrectly added to dynamic list Stewart Smith
2017-09-19 17:50 ` Rob Herring
2017-09-26 8:38 ` Stewart Smith
2017-09-26 8:40 ` [PATCH] drivers: of: increase MAX_RESERVED_REGIONS to 32 Stewart Smith
2017-10-02 22:58 ` Mauricio Faria de Oliveira [this message]
2017-10-12 17:25 ` 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=ddd472b4-6eea-80a3-53c6-bd63b565ff63@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=obh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=stewart@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).