From: Matthew Wilcox <willy@debian.org>
To: Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@debian.org>,
"Bagalkote, Sreenivas" <sreenib@lsil.com>,
"'Jeff Garzik'" <jgarzik@pobox.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH][RELEASE] megaraid 2.10.2 Driver
Date: Tue, 23 Mar 2004 13:30:35 +0000 [thread overview]
Message-ID: <20040323133035.GU25059@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040323062708.A29405@infradead.org>
On Tue, Mar 23, 2004 at 06:27:08AM +0000, Christoph Hellwig wrote:
> On Tue, Mar 23, 2004 at 12:45:43AM +0000, Matthew Wilcox wrote:
> > I don't think you understand how CONFIG_COMPAT works. x86-64 defines it
> > when it wants it:
>
> But not in 2.4, and this is a 2.4-only patch..
It is? I didn't see that mentioned anywhere.
Anyway, it's wrong to define LSI_CONFIG_COMPAT based solely on __x86_64__.
You'd also need to check IA32_EMULATION. Really, it would be simpler
to add CONFIG_COMPAT to 2.4.
--
"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-03-23 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 0:02 Bagalkote, Sreenivas
2004-03-23 0:45 ` Matthew Wilcox
2004-03-23 6:27 ` Christoph Hellwig
2004-03-23 13:30 ` Matthew Wilcox [this message]
2004-03-23 13:36 ` Christoph Hellwig
[not found] ` <20040324061553.GA13681@logos.cnet>
2004-03-24 20:39 ` Marcelo Tosatti
2004-04-17 2:15 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-03-23 16:00 Bagalkote, Sreenivas
2004-03-22 22:56 Bagalkote, Sreenivas
2004-03-22 23:07 ` Jeff Garzik
2004-03-23 8:12 ` Arjan van de Ven
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=20040323133035.GU25059@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sreenib@lsil.com \
/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