From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Nadav Amit <namit@vmware.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Cc: stable@vger.kernel.org
Cc: Borislav Petkov <bp@suse.de>
Cc: Toshi Kani <toshi.kani@hpe.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/3] resource: Fix locking in find_next_iomem_res()
Date: Sat, 15 Jun 2019 22:15:56 +0000 [thread overview]
Message-ID: <20190615221557.CD1492183F@mail.kernel.org> (raw)
In-Reply-To: <20190613045903.4922-2-namit@vmware.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: ff3cc952d3f0 resource: Add remove_resource interface.
The bot has tested the following trees: v5.1.9, v4.19.50, v4.14.125, v4.9.181.
v5.1.9: Build OK!
v4.19.50: Failed to apply! Possible dependencies:
010a93bf97c7 ("resource: Fix find_next_iomem_res() iteration issue")
a98959fdbda1 ("resource: Include resource end in walk_*() interfaces")
v4.14.125: Failed to apply! Possible dependencies:
010a93bf97c7 ("resource: Fix find_next_iomem_res() iteration issue")
0e4c12b45aa8 ("x86/mm, resource: Use PAGE_KERNEL protection for ioremap of memory pages")
1d2e733b13b4 ("resource: Provide resource struct in resource walk callback")
4ac2aed837cb ("resource: Consolidate resource walking code")
a98959fdbda1 ("resource: Include resource end in walk_*() interfaces")
v4.9.181: Failed to apply! Possible dependencies:
010a93bf97c7 ("resource: Fix find_next_iomem_res() iteration issue")
0e4c12b45aa8 ("x86/mm, resource: Use PAGE_KERNEL protection for ioremap of memory pages")
1d2e733b13b4 ("resource: Provide resource struct in resource walk callback")
4ac2aed837cb ("resource: Consolidate resource walking code")
60fe3910bb02 ("kexec_file: Allow arch-specific memory walking for kexec_add_buffer")
a0458284f062 ("powerpc: Add support code for kexec_file_load()")
a98959fdbda1 ("resource: Include resource end in walk_*() interfaces")
da6658859b9c ("powerpc: Change places using CONFIG_KEXEC to use CONFIG_KEXEC_CORE instead.")
ec2b9bfaac44 ("kexec_file: Change kexec_add_buffer to take kexec_buf as argument.")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-06-15 22:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 4:59 [PATCH 0/3] resource: find_next_iomem_res() improvements Nadav Amit
2019-06-13 4:59 ` [PATCH 1/3] resource: Fix locking in find_next_iomem_res() Nadav Amit
2019-06-15 22:15 ` Sasha Levin [this message]
2019-06-17 19:14 ` Nadav Amit
2019-06-18 0:55 ` Sasha Levin
2019-06-18 1:32 ` Nadav Amit
2019-06-18 4:26 ` Andrew Morton
2019-06-13 4:59 ` [PATCH 2/3] resource: Avoid unnecessary lookups " Nadav Amit
2019-06-13 4:59 ` [PATCH 3/3] resource: Introduce resource cache Nadav Amit
2019-06-15 22:16 ` Sasha Levin
2019-06-17 17:20 ` Nadav Amit
2019-06-18 4:57 ` Andrew Morton
2019-06-18 5:33 ` Nadav Amit
2019-06-18 5:40 ` Nadav Amit
2019-06-19 13:00 ` Bjorn Helgaas
2019-06-19 20:35 ` Nadav Amit
2019-06-19 21:53 ` Dan Williams
2019-06-20 21:31 ` Andi Kleen
2019-06-20 23:13 ` Dan Williams
2019-06-18 6:44 ` [PATCH 0/3] resource: find_next_iomem_res() improvements Dan Williams
2019-06-18 17:42 ` Nadav Amit
2019-06-18 18:30 ` Dan Williams
2019-06-18 21:56 ` Nadav Amit
2019-07-16 22:00 ` Andrew Morton
2019-07-16 22:06 ` Nadav Amit
2019-07-16 22:07 ` Dan Williams
2019-07-16 22:13 ` Nadav Amit
2019-07-16 22:20 ` Dan Williams
2019-07-16 22:28 ` Nadav Amit
2019-07-16 22:45 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190615221557.CD1492183F@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.