[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210527165355.GF8661@arm.com>
Date: Thu, 27 May 2021 17:53:56 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Marc Zyngier <maz@...nel.org>
Cc: kexec@...ts.infradead.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, 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: Re: [PATCH 2/4] kernel/resource: Populate child pointer in
find_next_iomem_res()
On Wed, May 26, 2021 at 08:05:29PM +0100, Marc Zyngier wrote:
> 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.
Did you mean "parse"? ;)
--
Catalin
Powered by blists - more mailing lists