From: Adrian Bunk <bunk@stusta.de>
To: philb@gnu.org, tim@cyberelk.net, campbell@torque.net, andrea@suse.de
Cc: linux-parport@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [2.6 patch] include/linux/parport_pc.h: "extern inline" -> "static inline"
Date: Sat, 19 Nov 2005 09:11:30 +0100 [thread overview]
Message-ID: <20051119081129.GH16060@stusta.de> (raw)
"extern inline" doesn't make much sense.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.15-rc1-mm2-full/include/linux/parport_pc.h.old 2005-11-19 02:33:28.000000000 +0100
+++ linux-2.6.15-rc1-mm2-full/include/linux/parport_pc.h 2005-11-19 02:33:44.000000000 +0100
@@ -79,7 +79,7 @@
}
#ifdef DEBUG_PARPORT
-extern __inline__ void dump_parport_state (char *str, struct parport *p)
+static inline void dump_parport_state (char *str, struct parport *p)
{
/* here's hoping that reading these ports won't side-effect anything underneath */
unsigned char ecr = inb (ECONTROL (p));
next reply other threads:[~2005-11-19 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 8:11 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-12 1:35 [2.6 patch] include/linux/parport_pc.h: "extern inline" -> "static inline" 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=20051119081129.GH16060@stusta.de \
--to=bunk@stusta.de \
--cc=andrea@suse.de \
--cc=campbell@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=philb@gnu.org \
--cc=tim@cyberelk.net \
/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