[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180928131043.GB21895@zn.tnic>
Date: Fri, 28 Sep 2018 15:10:43 +0200
From: Borislav Petkov <bp@...e.de>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: lijiang <lijiang@...hat.com>, dan.j.williams@...el.com,
brijesh.singh@....com, bhe@...hat.com, thomas.lendacky@....com,
tiwai@...e.de, x86@...nel.org, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, mingo@...hat.com,
baiyaowei@...s.chinamobile.com, hpa@...or.com, tglx@...utronix.de,
dyoung@...hat.com, akpm@...ux-foundation.org,
Vivek Goyal <vgoyal@...hat.com>
Subject: Re: [PATCH 3/3] resource: Fix find_next_iomem_res() iteration issue
On Thu, Sep 27, 2018 at 09:03:51AM -0500, Bjorn Helgaas wrote:
> Since I think the current interface (using *res as both input and
> output parameters that have very different meanings) is confusing,
FTR, I too, think that this whole machinery in resource.c with passing
in a function and a struct resource pointer and is clumsy and could use
a rewrite. When there's time... ;-\
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
Powered by blists - more mailing lists