* + firmware-memmap-pass-the-correct-argument-to-firmware_map_find_entry_bootmem.patch added to -mm tree
@ 2014-07-07 21:31 akpm
0 siblings, 0 replies; only message in thread
From: akpm @ 2014-07-07 21:31 UTC (permalink / raw)
To: isimatu.yasuaki, gregkh, santosh.shilimkar, toshi.kani, mm-commits
The patch titled
Subject: drivers/firmware/memmap.c: pass the correct argument to firmware_map_find_entry_bootmem()
has been added to the -mm tree. Its filename is
firmware-memmap-pass-the-correct-argument-to-firmware_map_find_entry_bootmem.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/firmware-memmap-pass-the-correct-argument-to-firmware_map_find_entry_bootmem.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/firmware-memmap-pass-the-correct-argument-to-firmware_map_find_entry_bootmem.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Subject: drivers/firmware/memmap.c: pass the correct argument to firmware_map_find_entry_bootmem()
firmware_map_add_hotplug() calls firmware_map_find_entry_bootmem() to get
free firmware_map_entry. But end arguments is not correct. So
firmware_map_find_entry_bootmem() cannot not find firmware_map_entry.
The patch passes the correct end argument to firmware_map_find_entry_bootmem().
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Toshi Kani <toshi.kani@hp.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/firmware/memmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/firmware/memmap.c~firmware-memmap-pass-the-correct-argument-to-firmware_map_find_entry_bootmem drivers/firmware/memmap.c
--- a/drivers/firmware/memmap.c~firmware-memmap-pass-the-correct-argument-to-firmware_map_find_entry_bootmem
+++ a/drivers/firmware/memmap.c
@@ -286,7 +286,7 @@ int __meminit firmware_map_add_hotplug(u
{
struct firmware_map_entry *entry;
- entry = firmware_map_find_entry_bootmem(start, end, type);
+ entry = firmware_map_find_entry_bootmem(start, end - 1, type);
if (!entry) {
entry = kzalloc(sizeof(struct firmware_map_entry), GFP_ATOMIC);
if (!entry)
_
Patches currently in -mm which might be from isimatu.yasuaki@jp.fujitsu.com are
x86mem-hotplug-pass-sync_global_pgds-a-correct-argument-in-remove_pagetable.patch
x86mem-hotplug-modify-pgd-entry-when-removing-memory.patch
x86-numa-setup_node_data-drop-dead-code-and-rename-function.patch
x86-numa-setup_node_data-drop-dead-code-and-rename-function-checkpatch-fixes.patch
mem-hotplug-avoid-illegal-state-prefixed-with-legal-state-when-changing-state-of-memory_block.patch
mem-hotplug-introduce-mmop_offline-to-replace-the-hard-coding-1.patch
firmware-memmap-pass-the-correct-argument-to-firmware_map_find_entry_bootmem.patch
dont-allocate-firmware_map_entry-of-same-memory-range.patch
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-07-07 21:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-07-07 21:31 + firmware-memmap-pass-the-correct-argument-to-firmware_map_find_entry_bootmem.patch added to -mm tree akpm
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.