From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] powerpc: Make isa_mem_base common to 32 and 64 bits
Date: Tue, 13 Nov 2007 20:55:24 +1100 [thread overview]
Message-ID: <1194947724.18185.97.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.62.0711130917350.31003@pademelon.sonytel.be>
> > +/* ISA Memory physical address (or 0 if none) */
> ^^^^^^^^^^^^
> > +resource_size_t isa_mem_base = 0;
>
> Let's hope this doesn't confuse too many people, as 0 is the valid value on
> legacy PC hardware ;-)
True, but that's been our default so far so I'm just not changing
existing behaviour. If it's bogus, it will need a separate fix.
Cheers,
Ben.
prev parent reply other threads:[~2007-11-13 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 4:43 [PATCH 1/2] powerpc: Make isa_mem_base common to 32 and 64 bits Benjamin Herrenschmidt
2007-11-13 8:18 ` Geert Uytterhoeven
2007-11-13 9:55 ` Benjamin Herrenschmidt [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=1194947724.18185.97.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).