From: Ralf Baechle <ralf@linux-mips.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] include/asm-mips/processor.h: "extern inline" -> "static inline"
Date: Mon, 9 Jul 2007 14:06:06 +0100 [thread overview]
Message-ID: <20070709130605.GA5467@linux-mips.org> (raw)
In-Reply-To: <20070709122240.GY3492@stusta.de>
On Mon, Jul 09, 2007 at 02:22:40PM +0200, Adrian Bunk wrote:
> In C99 (and therefore in gcc >= 4.3), "extern inline" means that the
> function should be compiled inline where the inline definition is seen,
> and that the compiler should also emit a copy of the function body with
> an externally visible symbol.
Uh, indeed. Thanks for the reminder. Patch applied.
Ralf
prev parent reply other threads:[~2007-07-09 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 1:03 [2.6 patch] include/asm-mips/processor.h: "extern inline" -> "static inline" Adrian Bunk
2007-07-09 10:27 ` Ralf Baechle
2007-07-09 11:40 ` Franck Bui-Huu
2007-07-09 12:22 ` Adrian Bunk
2007-07-09 13:06 ` Ralf Baechle [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=20070709130605.GA5467@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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