Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@mvista.com>
To: "Bradley D. LaRonde" <brad@ltc.com>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: Re: [Linux-mips-kernel]io.h patch
Date: 22 Mar 2002 18:02:12 -0800	[thread overview]
Message-ID: <1016848932.24387.317.camel@zeus> (raw)
In-Reply-To: <04c901c1d20d$bfb061e0$5601010a@prefect>

On Fri, 2002-03-22 at 17:55, Bradley D. LaRonde wrote:
> 
> ----- Original Message -----
> From: "Pete Popov" <ppopov@mvista.com>
> To: "sforge" <linux-mips-kernel@lists.sourceforge.net>
> Sent: Friday, March 22, 2002 8:11 PM
> Subject: [Linux-mips-kernel]io.h patch
> 
> 
> > Some of the macros in io.h cause compile problems in some of the drivers
> > because of the do while syntax.  I don't see any good reason why we
> > can't make those macros inline functions.  Any objections to this patch?
> 
> I pester Ralf about this from time to time.  The standing objection is that
> some older gccs don't do inline well.

That's all true and, in fact, I had run into a compiler problem some
time ago.  However, even then I was able to simply rearrange my C
routine a bit and then the compiler was happy.

Having pci-cardbus support on mips is kind of cool. Running wireless
cards off of it is even better.  Not being able to compile the drivers
because of io.h isn't.

Pete

      parent reply	other threads:[~2002-03-23  1:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1016845916.24217.298.camel@zeus>
2002-03-23  1:55 ` [Linux-mips-kernel]io.h patch Bradley D. LaRonde
2002-03-23  1:55   ` Bradley D. LaRonde
2002-03-23  2:02   ` Pete Popov [this message]

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=1016848932.24387.317.camel@zeus \
    --to=ppopov@mvista.com \
    --cc=brad@ltc.com \
    --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