From: James Bottomley <James.Bottomley@SteelEye.com>
To: Eric Dean Moore <Emoore@lsil.com>
Cc: Christoph Hellwig <hch@lst.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
"Shirron, Stephen" <Stephen.Shirron@lsil.com>
Subject: RE: fusion problems on 64bit hosts
Date: 27 Sep 2004 18:20:43 -0400 [thread overview]
Message-ID: <1096323650.2035.86.camel@mulgrave> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57050F84D0@exa-atlanta>
On Mon, 2004-09-27 at 18:12, Moore, Eric Dean wrote:
> No, we are not keeping a 64bit pointer in a 32bit hardware register.
> IMO we can solve this issue by adding ppc64 to define above.
Assuming this is the correct thing to do, what's wrong with predicating
on
#ifdef __LP64__
instead?
That way you don't have to keep this list of 64 bit architectures up to
date
James
next prev parent reply other threads:[~2004-09-27 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 22:12 fusion problems on 64bit hosts Moore, Eric Dean
2004-09-27 22:20 ` James Bottomley [this message]
2004-09-27 22:23 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2004-09-25 13:57 Christoph Hellwig
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=1096323650.2035.86.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Emoore@lsil.com \
--cc=Stephen.Shirron@lsil.com \
--cc=hch@lst.de \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox