From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Fri, 28 May 2021 09:06:43 +0100 Message-ID: <871r9r2sfg.wl-maz@kernel.org> From: Marc Zyngier Subject: Re: [PATCH 2/4] kernel/resource: Populate child pointer in find_next_iomem_res() In-Reply-To: <20210527165355.GF8661@arm.com> References: <20210526190531.62751-1-maz@kernel.org> <20210526190531.62751-3-maz@kernel.org> <20210527165355.GF8661@arm.com> MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") 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: Catalin Marinas Cc: kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, 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 On Thu, 27 May 2021 17:53:56 +0100, Catalin Marinas 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. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec