From: Juan Quintela <quintela@mandrakesoft.com>
To: Ralf Baechle <ralf@linux-mips.org>, mipslist <linux-mips@linux-mips.org>
Subject: [PATCH]: sgiserial 2/7 s/__INLINE__/inline/
Date: Thu, 27 Mar 2003 03:53:50 +0100 [thread overview]
Message-ID: <m28yv1eczl.fsf@mandrakesoft.com> (raw)
Hi
s/_INLINE_/inline/
build/drivers/sgi/char/sgiserial.c | 10 ++++------
1 files changed, 4 insertions(+), 6 deletions(-)
diff -puN build/drivers/sgi/char/sgiserial.c~sgiserial__INLINE_ build/drivers/sgi/char/sgiserial.c
--- 24/build/drivers/sgi/char/sgiserial.c~sgiserial__INLINE_ 2003-03-25 22:38:06.000000000 +0100
+++ 24-quintela/build/drivers/sgi/char/sgiserial.c 2003-03-25 22:39:04.000000000 +0100
@@ -118,8 +118,6 @@ static int serial_refcount;
#define RS_STROBE_TIME 10
#define RS_ISR_PASS_LIMIT 256
-#define _INLINE_ inline
-
static void change_speed(struct sgi_serial *info);
static struct tty_struct *serial_table[NUM_CHANNELS];
@@ -387,7 +385,7 @@ static inline void rs_recv_clear(struct
* This routine is used by the interrupt handler to schedule
* processing in the software interrupt portion of the driver.
*/
-static _INLINE_ void rs_sched_event(struct sgi_serial *info,
+static inline void rs_sched_event(struct sgi_serial *info,
int event)
{
info->event |= 1 << event;
@@ -399,7 +397,7 @@ static _INLINE_ void rs_sched_event(stru
extern void set_async_breakpoint(unsigned int epc);
#endif
-static _INLINE_ void receive_chars(struct sgi_serial *info, struct pt_regs *regs)
+static inline void receive_chars(struct sgi_serial *info, struct pt_regs *regs)
{
struct tty_struct *tty = info->tty;
volatile unsigned char junk;
@@ -460,7 +458,7 @@ clear_and_exit:
return;
}
-static _INLINE_ void transmit_chars(struct sgi_serial *info)
+static inline void transmit_chars(struct sgi_serial *info)
{
volatile unsigned char junk;
@@ -518,7 +516,7 @@ clear_and_return:
return;
}
-static _INLINE_ void status_handle(struct sgi_serial *info)
+static inline void status_handle(struct sgi_serial *info)
{
volatile unsigned char junk;
unsigned char status;
_
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
reply other threads:[~2003-03-27 2:56 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=m28yv1eczl.fsf@mandrakesoft.com \
--to=quintela@mandrakesoft.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.