From: Rob Herring <robh@kernel.org>
To: Quentin Perret <qperret@google.com>
Cc: robh+dt@kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org, frowand.list@gmail.com,
drinkcat@chromium.org, swboyd@chromium.org, karahmed@amazon.de,
f.fainelli@gmail.com, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] fdt: Properly handle "no-map" field in the memory region
Date: Fri, 15 Jan 2021 11:29:49 -0600 [thread overview]
Message-ID: <20210115172949.GA1495225@robh.at.kernel.org> (raw)
In-Reply-To: <20210115114544.1830068-2-qperret@google.com>
On Fri, 15 Jan 2021 11:45:43 +0000, Quentin Perret wrote:
> From: KarimAllah Ahmed <karahmed@amazon.de>
>
> Mark the memory region with NOMAP flag instead of completely removing it
> from the memory blocks. That makes the FDT handling consistent with the EFI
> memory map handling.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Frank Rowand <frowand.list@gmail.com>
> Cc: devicetree@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: KarimAllah Ahmed <karahmed@amazon.de>
> Signed-off-by: Quentin Perret <qperret@google.com>
> ---
> drivers/of/fdt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Applied, thanks!
next prev parent reply other threads:[~2021-01-15 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 11:45 [PATCH 0/2] fdt: A couple of no-map fixes Quentin Perret
2021-01-15 11:45 ` [PATCH 1/2] fdt: Properly handle "no-map" field in the memory region Quentin Perret
2021-01-15 17:29 ` Rob Herring [this message]
2021-01-15 11:45 ` [PATCH 2/2] of/fdt: Make sure no-map does not remove already reserved regions Quentin Perret
2021-01-15 17:30 ` Rob Herring
2021-01-16 0:30 ` Nicolas Boichat
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=20210115172949.GA1495225@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=karahmed@amazon.de \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qperret@google.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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.