Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Sender: "qperret via sendgmr" <qperret@r2d2-qp.c.googlers.com>
Date:   Fri, 15 Jan 2021 11:45:42 +0000
Message-Id: <20210115114544.1830068-1-qperret@google.com>
Mime-Version: 1.0
Subject: [PATCH 0/2] fdt: A couple of no-map fixes
From:   Quentin Perret <qperret@google.com>
To:     robh+dt@kernel.org, frowand.list@gmail.com
Cc:     devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
        drinkcat@chromium.org, swboyd@chromium.org, f.fainelli@gmail.com,
        karahmed@amazon.de, kernel-team@android.com
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

In the context of a KVM/arm64 thread [1], it became apparent that the
difference in behaviour of EFI and DT with respect to no-map regions was
something worth fixing.

Rob pointed out in that thread that a couple of patches in this area had
been sent but still needed to be integrated together, which is basically
what this series attempts to do.

 - Patch 01 is a generic fix that should make sense on its own;

 - Patch 02 allows the kernel to have a saner behaviour with a broken DT.
   This one had a small rebase conflict (caused by patch 01). I tested
   it in qemu and everything is looking good, the error message shows up
   in dmesg when it should.

Thanks,
Quentin

[1] https://lore.kernel.org/kvmarm/20210108121524.656872-1-qperret@google.com/

KarimAllah Ahmed (1):
  fdt: Properly handle "no-map" field in the memory region

Nicolas Boichat (1):
  of/fdt: Make sure no-map does not remove already reserved regions

 drivers/of/fdt.c | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

-- 
2.30.0.284.gd98b1dd5eaa7-goog