From: "Bryan O'Sullivan" <bos@pathscale.com>
To: linux-kernel@vger.kernel.org
Subject: Correct Kbuild way to handle arches that don't implement readq/writeq?
Date: Mon, 02 Jan 2006 10:10:14 -0800 [thread overview]
Message-ID: <1136225414.20330.25.camel@serpentine.pathscale.com> (raw)
One of the requests during the first round of InfiniPath driver review
was to compile the driver on a 32-bit platform. Our driver requires
64-bit MMIO operations (readq and writeq) that are not available on some
arches, such as i386, and which can't be emulated safely in terms of
32-bit operations.
What's the correct way to get the driver to not compile on such
platforms? Do I use CONFIG_64BIT as a proxy for "has readq and writeq"?
<b
reply other threads:[~2006-01-02 18:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1136225414.20330.25.camel@serpentine.pathscale.com \
--to=bos@pathscale.com \
--cc=linux-kernel@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
Powered by JetHome