From: Andrew Grover <andy.grover@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: "extern inline" purge? was: Re: [PATCH] fix "extern inline"
Date: Tue, 30 Nov 2004 17:33:17 -0800 [thread overview]
Message-ID: <c0a09e5c04113017333c85c7e2@mail.gmail.com> (raw)
In-Reply-To: <m2y8hapakk.wl%ysato@users.sourceforge.jp>
On Wed, 10 Nov 2004 13:55:23 +0900, Yoshinori Sato
<ysato@users.sourceforge.jp> wrote:
> Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
> -extern __inline__ int generic_fls(int x)
> +static __inline__ int generic_fls(int x)
Along the lines of this patch, can I ask... if a patch were created to
replace all instances of "extern inline" with "static inline" would
that be a good thing or a waste of time? I found a 3 year old thread
(Jul 27 2001, "Re: [PATCH] gcc-3.0.1 and 2.4.7-ac1") where it sounded
like a good thing to do, but obviously there are some still around.
Regards -- Andy
next prev parent reply other threads:[~2004-12-01 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 4:55 Yoshinori Sato
2004-12-01 1:33 ` Andrew Grover [this message]
2004-12-01 8:43 ` "extern inline" purge? was: " Arnd Bergmann
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=c0a09e5c04113017333c85c7e2@mail.gmail.com \
--to=andy.grover@gmail.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
Powered by JetHome