From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: horms@verge.net.au, tony.luck@intel.com
Subject: + ia64-vmcore_find_descriptor_size-should-be-in-__init.patch added to -mm tree
Date: Tue, 30 Oct 2007 13:12:55 -0700 [thread overview]
Message-ID: <200710302012.l9UKCt90025930@imap1.linux-foundation.org> (raw)
The patch titled
ia64: vmcore_find_descriptor_size should be in __init
has been added to the -mm tree. Its filename is
ia64-vmcore_find_descriptor_size-should-be-in-__init.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: ia64: vmcore_find_descriptor_size should be in __init
From: Simon Horman <horms@verge.net.au>
vmcore_find_descriptor_size() is only called by reserve_elfcorehdr(), which
is in __init, so it seems to me that vmcore_find_descriptor_size() should
be there too.
Signed-off-by: Simon Horman <horms@verge.net.au>
Cc: "Luck, Tony" <tony.luck@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/ia64/kernel/efi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN arch/ia64/kernel/efi.c~ia64-vmcore_find_descriptor_size-should-be-in-__init arch/ia64/kernel/efi.c
--- a/arch/ia64/kernel/efi.c~ia64-vmcore_find_descriptor_size-should-be-in-__init
+++ a/arch/ia64/kernel/efi.c
@@ -1231,7 +1231,7 @@ kdump_find_rsvd_region (unsigned long si
#ifdef CONFIG_PROC_VMCORE
/* locate the size find a the descriptor at a certain address */
-unsigned long
+unsigned long __init
vmcore_find_descriptor_size (unsigned long address)
{
void *efi_map_start, *efi_map_end, *p;
_
Patches currently in -mm which might be from horms@verge.net.au are
origin.patch
ia64-vmcore_find_descriptor_size-should-be-in-__init.patch
reply other threads:[~2007-10-30 20:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200710302012.l9UKCt90025930@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tony.luck@intel.com \
/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.