From: p.pisati@gmail.com (Paolo Pisati)
To: linux-arm-kernel@lists.infradead.org
Subject: 4.19-rcX: WARN_ON() arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
Date: Tue, 9 Oct 2018 11:24:32 +0200 [thread overview]
Message-ID: <20181009092432.GA10312@harukaze> (raw)
In-Reply-To: <47fa0375-ed69-0cbc-9dcb-0cafb9184f24@arm.com>
On Mon, Oct 08, 2018 at 05:03:27PM +0100, James Morse wrote:
> But! DT's that have this reserved-but-not-memory are already out there, so we
> should work around this in the kernel.
Ack, thanks for the explanation.
--
bye,
p.
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Pisati <p.pisati@gmail.com>
To: James Morse <james.morse@arm.com>
Cc: Paolo Pisati <p.pisati@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: 4.19-rcX: WARN_ON() arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
Date: Tue, 9 Oct 2018 11:24:32 +0200 [thread overview]
Message-ID: <20181009092432.GA10312@harukaze> (raw)
In-Reply-To: <47fa0375-ed69-0cbc-9dcb-0cafb9184f24@arm.com>
On Mon, Oct 08, 2018 at 05:03:27PM +0100, James Morse wrote:
> But! DT's that have this reserved-but-not-memory are already out there, so we
> should work around this in the kernel.
Ack, thanks for the explanation.
--
bye,
p.
next prev parent reply other threads:[~2018-10-09 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 15:11 4.19-rcX: WARN_ON() arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions Paolo Pisati
2018-10-08 15:11 ` Paolo Pisati
2018-10-08 16:03 ` James Morse
2018-10-08 16:03 ` James Morse
2018-10-09 9:24 ` Paolo Pisati [this message]
2018-10-09 9:24 ` Paolo Pisati
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=20181009092432.GA10312@harukaze \
--to=p.pisati@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.