fdt: A couple of no-map fixes
Status from this message: Applied, thanks!
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | fdt: Properly handle "no-map" field in the memory regiondrivers/ | +1 | 1 reply | |
| 2/2 | of/fdt: Make sure no-map does not remove already reserved regionsdrivers/ | +9 | 2 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Stephen Boyd |
|---|---|
| 1/2 | |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] fdt: A couple of no-map fixes
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/[email protected]/
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(-)
Signature · 1 line
2.30.0.284.gd98b1dd5eaa7-goog