From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Thomas Gleixner <tglx@linutronix.de>,
David Howells <dhowells@redhat.com>,
Koichi Yasutake <yasutake.koichi@jp.panasonic.com>
Cc: linux-am33-list@redhat.com, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH] mn10300: Fix common threadinfo allocator fallout
Date: Wed, 20 Jun 2012 13:57:46 +0200 [thread overview]
Message-ID: <1340193466-3342-1-git-send-email-geert@linux-m68k.org> (raw)
commit c03a6a7ba6f456663e4b254cdde460b24c0852e1 ("mn10300: Use common
threadinfo allocator") caused:
include/linux/thread_info.h: In function 'arch_release_thread_info':
include/linux/thread_info.h:70:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
include/linux/thread_info.h:75:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
include/linux/thread_info.h:80:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
include/linux/thread_info.h:85:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
include/linux/thread_info.h:90:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
include/linux/thread_info.h:127:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
include/linux/thread_info.h:132:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
include/linux/thread_info.h:136:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
include/linux/thread_info.h:140:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
Add the missing semicolon, and revive the "extern" while we're at it.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
arch/mn10300/include/asm/thread_info.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/mn10300/include/asm/thread_info.h b/arch/mn10300/include/asm/thread_info.h
index 08251d6..f374a76 100644
--- a/arch/mn10300/include/asm/thread_info.h
+++ b/arch/mn10300/include/asm/thread_info.h
@@ -123,7 +123,7 @@ static inline unsigned long current_stack_pointer(void)
}
#ifndef CONFIG_KGDB
-void arch_release_thread_info(struct thread_info *ti)
+extern void arch_release_thread_info(struct thread_info *ti);
#endif
#define get_thread_info(ti) get_task_struct((ti)->task)
#define put_thread_info(ti) put_task_struct((ti)->task)
--
1.7.0.4
reply other threads:[~2012-06-20 11:57 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=1340193466-3342-1-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=dhowells@redhat.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yasutake.koichi@jp.panasonic.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 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®