From: tip-bot for Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, h-shimamoto@ct.jp.nec.com,
hpa@zytor.com, mingo@redhat.com, fujita.tomonori@lab.ntt.co.jp,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:core/iommu] x86: Don't put iommu_shutdown_noop() in init section
Date: Mon, 16 Nov 2009 09:03:46 GMT [thread overview]
Message-ID: <tip-62ad33f67003b9a7b6013f0511579b9805e11626@git.kernel.org> (raw)
In-Reply-To: <4B00BC8E.50801@ct.jp.nec.com>
Commit-ID: 62ad33f67003b9a7b6013f0511579b9805e11626
Gitweb: http://git.kernel.org/tip/62ad33f67003b9a7b6013f0511579b9805e11626
Author: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
AuthorDate: Mon, 16 Nov 2009 11:44:30 +0900
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Mon, 16 Nov 2009 08:58:51 +0100
x86: Don't put iommu_shutdown_noop() in init section
It causes kernel panic on shutdown or reboot.
Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Acked-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
LKML-Reference: <4B00BC8E.50801@ct.jp.nec.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/x86_init.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/x86_init.c b/arch/x86/kernel/x86_init.c
index 80f3ae2..d11c5ff 100644
--- a/arch/x86/kernel/x86_init.c
+++ b/arch/x86/kernel/x86_init.c
@@ -20,7 +20,7 @@ void __cpuinit x86_init_noop(void) { }
void __init x86_init_uint_noop(unsigned int unused) { }
void __init x86_init_pgd_noop(pgd_t *unused) { }
int __init iommu_init_noop(void) { return 0; }
-void __init iommu_shutdown_noop(void) { }
+void iommu_shutdown_noop(void) { }
/*
* The platform setup functions are preset with the default functions
prev parent reply other threads:[~2009-11-16 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 2:44 [PATCH] " Hiroshi Shimamoto
2009-11-16 3:49 ` FUJITA Tomonori
2009-11-16 9:03 ` tip-bot for Hiroshi Shimamoto [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-62ad33f67003b9a7b6013f0511579b9805e11626@git.kernel.org \
--to=h-shimamoto@ct.jp.nec.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--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
Powered by JetHome