From: Matthew Wilcox <willy@debian.org>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: "'Arjan van de Ven'" <arjanv@redhat.com>,
"'Christoph Hellwig'" <hch@infradead.org>,
"'James Bottomley'" <James.Bottomley@SteelEye.com>,
"'matt_domsch@dell.com'" <matt_domsch@dell.com>,
"'Paul Wagland'" <paul@wagland.net>,
Matthew Wilcox <willy@debian.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: [SUBJECT CHANGE]: megaraid unified driver version 2.20.0.0-alpha1
Date: Wed, 25 Feb 2004 12:58:10 +0000 [thread overview]
Message-ID: <20040225125810.GT25779@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC3E2@exa-atlanta.se.lsil.com>
On Tue, Feb 24, 2004 at 07:34:01PM -0500, Mukker, Atul wrote:
> 6. Single code to support *all* x86-32, IA64, and x86-64 platforms
No. Megaraid is a PCI card. Therefore this one codebase should support
*all* PCI-capable architectures, not just these three. Nobody's requiring
that you test on all the weird and wonderful architectures out there, just
that you don't do things like
#if defined(__x86_64__) || defined(__ia64__)
#endif
when you really mean
#ifdef CONFIG_COMPAT
#endif
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-02-25 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 0:34 Mukker, Atul
2004-02-25 12:58 ` Matthew Wilcox [this message]
2004-02-25 13:16 ` 'Christoph Hellwig'
2004-02-25 17:28 ` Matt Domsch
2004-02-25 17:35 ` Matthew Wilcox
2004-02-25 19:03 ` Matt Domsch
2004-02-25 14:28 ` Paul Wagland
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=20040225125810.GT25779@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=Atulm@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=arjanv@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matt_domsch@dell.com \
--cc=paul@wagland.net \
/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
all inboxes | Powered by JetHome®