From: Juan Quintela <quintela@mandrakesoft.com>
To: Ralf Baechle <ralf@linux-mips.org>, mipslist <linux-mips@linux-mips.org>
Subject: [PATCH]: sgiserial 1/7: flags are unsigned long
Date: Thu, 27 Mar 2003 03:53:43 +0100 [thread overview]
Message-ID: <m2adfheczs.fsf@mandrakesoft.com> (raw)
Hi
flags should be long, not int.
build/drivers/sgi/char/sgiserial.c | 9 ++++++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff -puN build/drivers/sgi/char/sgiserial.c~sgserial_flags build/drivers/sgi/char/sgiserial.c
--- 24/build/drivers/sgi/char/sgiserial.c~sgserial_flags 2003-03-22 01:37:45.000000000 +0100
+++ 24-quintela/build/drivers/sgi/char/sgiserial.c 2003-03-22 01:43:17.000000000 +0100
@@ -886,7 +886,8 @@ static void zs_cons_put_char(char ch)
{
struct sgi_zschannel *chan = zs_conschan;
volatile unsigned char junk;
- int flags, loops = 0;
+ unsigned long flags;
+ int loops = 0;
save_flags(flags); cli();
while(((junk = chan->control) & Tx_BUF_EMP)==0 && loops < 10000) {
@@ -911,7 +912,8 @@ static void rs_put_char(struct tty_struc
struct sgi_zschannel *chan =
((struct sgi_serial *)tty->driver_data)->zs_channel;
volatile unsigned char junk;
- int flags, loops = 0;
+ unsigned long flags;
+ int loops = 0;
save_flags(flags); cli();
while(((junk = chan->control) & Tx_BUF_EMP)==0 && loops < 10000) {
@@ -1854,7 +1856,8 @@ volatile int test_done;
/* rs_init inits the driver */
int rs_init(void)
{
- int chip, channel, i, flags;
+ unsigned long flags;
+ int chip, channel, i;
struct sgi_serial *info;
_
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next reply other threads:[~2003-03-27 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 2:53 Juan Quintela [this message]
2003-03-27 12:44 ` [PATCH]: sgiserial 1/7: flags are unsigned long Ralf Baechle
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=m2adfheczs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox