[PATCH 3/3] resource: Fix find_next_iomem_res() iteration issue
bp at suse.de
Tue Oct 9 10:35:26 PDT 2018
On Tue, Oct 09, 2018 at 12:30:33PM -0500, Bjorn Helgaas wrote:
> Sorry, I don't know what happened here because I didn't see these
> comments until today. I suspect what happened was that my Gmail
> filter auto-filed them in my linux-kernel folder, which I don't read.
> On my @google.com account, I have another filter that pull out things
> addressed directly to me, which I *do* read. But this thread didn't
> cc that account until the tip-bot message, which *did* cc my @google
> account because that's how I signed off the patches. Sigh.
No worries, it all should be taken care of now! :-)
> Anyway, it looks like this stuff is on its way; let me know
> (bhelgaas at google.com) if I should do anything else. I would address
> your comments above, but since this seems to be applied and I saw a
> cleanup patch from you, I assume you already took care of them.
Yeah, I think I've covered them all but if you see something out of the
ordinary, let me know so that I can fix it.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
More information about the kexec