From: Pete Popov <ppopov@mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Guillermo A. Loyola" <gmo@broadcom.com>,
linux-mips <linux-mips@oss.sgi.com>,
sforge <linux-mips-kernel@lists.sourceforge.net>
Subject: Re: pcmcia
Date: 30 Nov 2001 09:50:51 -0800 [thread overview]
Message-ID: <1007142651.6016.148.camel@zeus> (raw)
In-Reply-To: <E169rrU-0004GN-00@the-village.bc.nu>
On Fri, 2001-11-30 at 09:54, Alan Cox wrote:
> > > We need the same here, how about doing this instead:
> > >
> > > #ifdef __i386__
> > > typedef u_short ioaddr_t;
> > > #else
> > > typedef u_int ioaddr_t;
> > > #endif
> >
> > That probably makes more sense. I wasn't sure if it's only x86 that
> > needs? ioaddr_t to be a 16 bit type.
>
> Is there any platform where making it int actually -breaks-.
I can't see how it would break anything ... but I've said that before.
It's not a variable which maps a hardware register, a protocol field,
etc, so it should be safe to just make it an int.
> At least for 2.5 it would seem a lot saner to just make it bigger and see
Pete
next prev parent reply other threads:[~2001-11-30 18:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-30 8:39 pcmcia Guillermo A. Loyola
2001-11-30 17:35 ` pcmcia Pete Popov
2001-11-30 17:54 ` pcmcia Alan Cox
2001-11-30 17:54 ` pcmcia Alan Cox
2001-11-30 17:50 ` Pete Popov [this message]
[not found] <se6c604d.015@mail.frequentis.com>
2003-03-10 9:01 ` PCMCIA Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-03-10 8:18 PCMCIA Gerhard TAEUBL
2003-03-10 8:45 ` PCMCIA Wolfgang Denk
2003-03-07 7:32 PCMCIA Gerhard TAEUBL
2003-03-07 17:18 ` PCMCIA Magnus Damm
2003-03-07 19:53 ` PCMCIA Wolfgang Denk
2003-03-04 10:36 PCMCIA Gerhard TAEUBL
2001-11-29 20:32 pcmcia Pete Popov
2000-11-08 22:24 pcmcia David Feuer
2000-11-08 22:39 ` pcmcia Jeff Garzik
2000-11-08 23:59 ` pcmcia David Ford
2000-11-09 0:35 ` pcmcia Brett
2000-11-09 1:15 ` pcmcia David Ford
2000-11-09 2:44 ` pcmcia FORT David
2000-11-09 2:19 ` pcmcia Horst von Brand
2000-02-05 19:21 PCMCIA Ryan Boder
1999-12-23 3:28 PCMCIA Nguyen Xuan Hoang
2000-06-23 7:55 ` PCMCIA Jo-Ellen F. Mathews
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=1007142651.6016.148.camel@zeus \
--to=ppopov@mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gmo@broadcom.com \
--cc=linux-mips-kernel@lists.sourceforge.net \
--cc=linux-mips@oss.sgi.com \
/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.