[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210526190531.62751-3-maz@kernel.org>
Date: Wed, 26 May 2021 20:05:29 +0100
From: Marc Zyngier <maz@...nel.org>
To: kexec@...ts.infradead.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Ard Biesheuvel <ardb@...nel.org>,
Mark Rutland <mark.rutland@....com>,
James Morse <james.morse@....com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Hanjun Guo <guohanjun@...wei.com>,
Sudeep Holla <sudeep.holla@....com>,
Eric Biederman <ebiederm@...ssion.com>,
Bhupesh SHARMA <bhupesh.sharma@...aro.org>,
AKASHI Takahiro <takahiro.akashi@...aro.org>,
Dave Young <dyoung@...hat.com>,
Moritz Fischer <mdf@...nel.org>, kernel-team@...roid.com
Subject: [PATCH 2/4] kernel/resource: Populate child pointer in find_next_iomem_res()
When find_next_iomem_res() returns a resource, it doesn't
populate the child pointer (but does so with the parent).
As we are about to need to arse child resources, populate
this pointer as well.
Signed-off-by: Marc Zyngier <maz@...nel.org>
---
kernel/resource.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/resource.c b/kernel/resource.c
index ca9f5198a01f..311b8d2c9957 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -377,6 +377,7 @@ static int find_next_iomem_res(resource_size_t start, resource_size_t end,
.flags = p->flags,
.desc = p->desc,
.parent = p->parent,
+ .child = p->child,
};
}
--
2.30.2
Powered by blists - more mailing lists