From: Pete Popov <ppopov@mvista.com>
To: "Guillermo A. Loyola" <gmo@broadcom.com>
Cc: linux-mips <linux-mips@oss.sgi.com>,
sforge <linux-mips-kernel@lists.sourceforge.net>
Subject: RE: pcmcia
Date: 30 Nov 2001 09:35:01 -0800 [thread overview]
Message-ID: <1007141701.22949.140.camel@zeus> (raw)
In-Reply-To: <E1EBEF4633DBD3118AD1009027E2FFA0025D0513@mail.sv.broadcom.com>
On Fri, 2001-11-30 at 00:39, Guillermo A. Loyola wrote:
> > The pcmcia variable ioaddr_t should be a 32 bit type for my socket
> > driver. Is there any harm to other mips pcmcia socket drivers if we
> > apply the patch below?
>
> 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.
Pete
next prev parent reply other threads:[~2001-11-30 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-30 8:39 pcmcia Guillermo A. Loyola
2001-11-30 17:35 ` Pete Popov [this message]
2001-11-30 17:54 ` pcmcia Alan Cox
2001-11-30 17:50 ` pcmcia Pete Popov
2001-11-30 17:54 ` pcmcia Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-11-29 20:32 pcmcia Pete Popov
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=1007141701.22949.140.camel@zeus \
--to=ppopov@mvista.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox