From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [patch] move machvec_noop from inline to c file
Date: Sun, 12 Mar 2006 18:23:37 +0000 [thread overview]
Message-ID: <200603121823.k2CINZg10902@unix-os.sc.intel.com> (raw)
There are 9 copy of these thing when compile with CONFIG_IA64_GENERIC
because it is declared as inline function but called through function
pointer. gcc makes 9 copy of these empty function around. Move it
into machvec.c file.
Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
--- ./arch/ia64/kernel/machvec.c.orig 2006-01-02 19:21:10.000000000 -0800
+++ ./arch/ia64/kernel/machvec.c 2006-03-12 10:54:23.311711322 -0800
@@ -41,6 +41,13 @@ machvec_init (const char *name)
printk(KERN_INFO "booting generic kernel on platform %s\n", name);
}
+void machvec_noop (void)
+{
+}
+
+void machvec_noop_mm (struct mm_struct *mm)
+{
+}
#endif /* CONFIG_IA64_GENERIC */
void
--- ./include/asm-ia64/machvec.h.orig 2006-01-02 19:21:10.000000000 -0800
+++ ./include/asm-ia64/machvec.h 2006-03-12 11:07:24.618342376 -0800
@@ -75,6 +75,10 @@ typedef unsigned short ia64_mv_readw_rel
typedef unsigned int ia64_mv_readl_relaxed_t (const volatile void __iomem *);
typedef unsigned long ia64_mv_readq_relaxed_t (const volatile void __iomem *);
+#if defined (CONFIG_IA64_GENERIC)
+extern void machvec_noop (void);
+extern void machvec_noop_mm (struct mm_struct *mm);
+#else
static inline void
machvec_noop (void)
{
@@ -84,6 +88,7 @@ static inline void
machvec_noop_mm (struct mm_struct *mm)
{
}
+#endif
extern void machvec_setup (char **);
extern void machvec_timer_interrupt (int, void *, struct pt_regs *);
reply other threads:[~2006-03-12 18:23 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=200603121823.k2CINZg10902@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox