[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <871r9r2sfg.wl-maz@kernel.org>
Date: Fri, 28 May 2021 09:06:43 +0100
From: Marc Zyngier <maz@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>
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 Thu, 27 May 2021 17:53:56 +0100,
Catalin Marinas <catalin.marinas@....com> wrote:
>
> 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"? ;)
This is so embarrassing... :-/ Let me fix that right now.
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists