From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Marc Zyngier Subject: [PATCH 2/4] kernel/resource: Populate child pointer in find_next_iomem_res() Date: Wed, 26 May 2021 20:05:29 +0100 Message-Id: <20210526190531.62751-3-maz@kernel.org> In-Reply-To: <20210526190531.62751-1-maz@kernel.org> References: <20210526190531.62751-1-maz@kernel.org> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Catalin Marinas , Will Deacon , Ard Biesheuvel , Mark Rutland , James Morse , Lorenzo Pieralisi , Hanjun Guo , Sudeep Holla , Eric Biederman , Bhupesh SHARMA , AKASHI Takahiro , Dave Young , Moritz Fischer , kernel-team@android.com 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 --- 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 _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec