From: Al Viro <viro@ftp.linux.org.uk>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rio: switch to ANSI prototypes
Date: Thu, 29 Sep 2005 16:25:56 +0100 [thread overview]
Message-ID: <20050929152556.GU7992@ftp.linux.org.uk> (raw)
In-Reply-To: <20050929152208.GA18132@mipter.zuzino.mipt.ru>
On Thu, Sep 29, 2005 at 07:22:08PM +0400, Alexey Dobriyan wrote:
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
>
> drivers/char/rio/rioboot.c | 25 +++++--------------------
> drivers/char/rio/rioctrl.c | 12 ++----------
> drivers/char/rio/rioinit.c | 27 +++++----------------------
> drivers/char/rio/riointr.c | 12 +++---------
> drivers/char/rio/rioparam.c | 24 ++++++------------------
> drivers/char/rio/rioroute.c | 34 +++++++---------------------------
> drivers/char/rio/riotable.c | 19 +++++--------------
> drivers/char/rio/riotty.c | 3 +--
> 8 files changed, 34 insertions(+), 122 deletions(-)
Uh-oh... Well, if you want to play with it... FWIW, I'm disabling rio as
hopeless FPOS; if you feel masochistic, go ahead but keep in mind that its
handling of tty glue is severely b0rken.
> int
> -RIOBootCodeHOST(p, rbp)
> -struct rio_info * p;
> -register struct DownLoad *rbp;
> +RIOBootCodeHOST(struct rio_info *p, register struct DownLoad *rbp)
s/register//
> @@ -151,12 +151,7 @@ static int copyout (caddr_t dp, int arg,
> }
>
> int
> -riocontrol(p, dev, cmd, arg, su)
> -struct rio_info * p;
> -dev_t dev;
> -int cmd;
> -caddr_t arg;
> -int su;
> +riocontrol(struct rio_info *p, dev_t dev, int cmd, caddr_t arg, int su)
Use of dev_t here is almost certainly broken. Use of caddr_t is *always*
broken.
next prev parent reply other threads:[~2005-09-29 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 15:22 [PATCH] rio: switch to ANSI prototypes Alexey Dobriyan
2005-09-29 15:25 ` Al Viro [this message]
2005-09-29 16:52 ` Alexey Dobriyan
2005-09-29 16:52 ` Al Viro
2005-09-29 19:23 ` Bill Davidsen
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=20050929152556.GU7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--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 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.