public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: bryan.wu@analog.com
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] blackfin: "extern inline" -> "static inline"
Date: Wed, 24 Oct 2007 18:26:43 +0200	[thread overview]
Message-ID: <20071024162643.GP30533@stusta.de> (raw)

"extern inline" will have different semantics with gcc 4.3.

Signed-off-by: Adrian Bunk <bunk@kernel.org>

---

 include/asm-blackfin/string.h |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

f2a6901348a61a13fc19a01f5584406190302919 
diff --git a/include/asm-blackfin/string.h b/include/asm-blackfin/string.h
index e8ada91..e4703a7 100644
--- a/include/asm-blackfin/string.h
+++ b/include/asm-blackfin/string.h
@@ -4,7 +4,7 @@
 #ifdef __KERNEL__		/* only set these up for kernel code */
 
 #define __HAVE_ARCH_STRCPY
-extern inline char *strcpy(char *dest, const char *src)
+static inline char *strcpy(char *dest, const char *src)
 {
 	char *xdest = dest;
 	char temp = 0;
@@ -23,7 +23,7 @@ extern inline char *strcpy(char *dest, const char *src)
 }
 
 #define __HAVE_ARCH_STRNCPY
-extern inline char *strncpy(char *dest, const char *src, size_t n)
+static inline char *strncpy(char *dest, const char *src, size_t n)
 {
 	char *xdest = dest;
 	char temp = 0;
@@ -59,7 +59,7 @@ extern inline char *strncpy(char *dest, const char *src, size_t n)
 }
 
 #define __HAVE_ARCH_STRCMP
-extern inline int strcmp(const char *cs, const char *ct)
+static inline int strcmp(const char *cs, const char *ct)
 {
 	/* need to use int's here so the char's in the assembly don't get
 	 * sign extended incorrectly when we don't want them to be
@@ -86,7 +86,7 @@ extern inline int strcmp(const char *cs, const char *ct)
 }
 
 #define __HAVE_ARCH_STRNCMP
-extern inline int strncmp(const char *cs, const char *ct, size_t count)
+static inline int strncmp(const char *cs, const char *ct, size_t count)
 {
 	/* need to use int's here so the char's in the assembly don't get
 	 * sign extended incorrectly when we don't want them to be


             reply	other threads:[~2007-10-24 16:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 16:26 Adrian Bunk [this message]
2007-10-25  2:47 ` [2.6 patch] blackfin: "extern inline" -> "static inline" Jie Zhang
2007-10-25  3:00   ` Mike Frysinger
2007-10-25  3:06     ` H. Peter Anvin
2007-10-25  3:17       ` Mike Frysinger
2007-10-25 15:05       ` Adrian Bunk
2007-10-25 16:16         ` Mike Frysinger
2007-10-25 16:53           ` Adrian Bunk
2007-10-25 20:07             ` Mike Frysinger
2007-10-25 20:18               ` Adrian Bunk
2007-10-25 20:20                 ` Mike Frysinger
2007-10-25 20:28                   ` H. Peter Anvin
2007-10-25 20:45                     ` Mike Frysinger
2007-10-25 20:53                       ` H. Peter Anvin
2007-10-25 20:47                     ` Adrian Bunk
2007-10-25 20:54                       ` H. Peter Anvin
2007-10-25 20:46                   ` Adrian Bunk

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=20071024162643.GP30533@stusta.de \
    --to=bunk@kernel.org \
    --cc=bryan.wu@analog.com \
    --cc=linux-kernel@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