From: tip-bot for Jan Beulich <JBeulich@suse.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
jbeulich@suse.com, JBeulich@suse.com, tglx@linutronix.de
Subject: [tip:x86/debug] x86/mm: Mark free_initrd_mem() as __init
Date: Wed, 20 Jun 2012 10:06:14 -0700 [thread overview]
Message-ID: <tip-0d26d1d873a302828e064737746c53a2689e6c0f@git.kernel.org> (raw)
In-Reply-To: <4FDF1F5C020000780008A661@nat28.tlf.novell.com>
Commit-ID: 0d26d1d873a302828e064737746c53a2689e6c0f
Gitweb: http://git.kernel.org/tip/0d26d1d873a302828e064737746c53a2689e6c0f
Author: Jan Beulich <JBeulich@suse.com>
AuthorDate: Mon, 18 Jun 2012 11:30:20 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 20 Jun 2012 14:33:47 +0200
x86/mm: Mark free_initrd_mem() as __init
... matching various other architectures.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Link: http://lkml.kernel.org/r/4FDF1F5C020000780008A661@nat28.tlf.novell.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
arch/x86/mm/init.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index bc4e9d8..e0e6990 100644
--- a/arch/x86/mm/init.c
+++ b/arch/x86/mm/init.c
@@ -385,7 +385,7 @@ void free_initmem(void)
}
#ifdef CONFIG_BLK_DEV_INITRD
-void free_initrd_mem(unsigned long start, unsigned long end)
+void __init free_initrd_mem(unsigned long start, unsigned long end)
{
/*
* end could be not aligned, and We can not align that,
prev parent reply other threads:[~2012-06-20 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 10:30 [PATCH] x86: free_initrd_mem() can be __init Jan Beulich
2012-06-20 17:06 ` tip-bot for Jan Beulich [this message]
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=tip-0d26d1d873a302828e064737746c53a2689e6c0f@git.kernel.org \
--to=jbeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®