From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: megaraid warnings
Date: Tue, 17 Feb 2004 20:08:22 +0000 [thread overview]
Message-ID: <16434.29878.769928.305667@napali.hpl.hp.com> (raw)
In-Reply-To: <16434.28509.327706.76307@napali.hpl.hp.com>
>>>>> On Tue, 17 Feb 2004 19:58:47 +0000, Matthew Wilcox <willy@debian.org> said:
Matthew> This keeps coming up on linux-scsi; basically these are
Matthew> ioctls that are called by some binary-only (and
Matthew> x86-binary-only at that) management program. so if they
Matthew> want to ship an ia64 version of their management program,
Matthew> they'll have to fix this; otherwise the addresses are
Matthew> guaranteed to be in the lower 32 bits of the address space.
Then why not disable the offending code for 64-bit platforms for the
time being?
--david
next prev parent reply other threads:[~2004-02-17 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 19:45 megaraid warnings David Mosberger
2004-02-17 19:58 ` Matthew Wilcox
2004-02-17 20:08 ` David Mosberger [this message]
2004-02-17 20:09 ` Matthew Wilcox
2004-02-17 20:18 ` David Mosberger
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=16434.29878.769928.305667@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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