From: Matthew Wilcox <willy@debian.org>
To: hch@infradead.org
Cc: Jeff Garzik <jgarzik@pobox.com>,
James Bottomley <James.Bottomley@steeleye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: ahc1542 fun
Date: Wed, 26 May 2004 18:52:17 +0100 [thread overview]
Message-ID: <20040526175217.GU29154@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040526064430.GA21531@infradead.org>
On Wed, May 26, 2004 at 02:44:30AM -0400, hch@infradead.org wrote:
> This needs fixing in mca.h and mca-legacy.h. The debian kernel package
> has a fix that I don't quite like. I'll rework it in the next days and
> submit it.
What I have in the PA tree is:
Index: include/linux/mca.h
===================================================================
RCS file: /var/cvs/linux-2.6/include/linux/mca.h,v
retrieving revision 1.4.46.1
retrieving revision 1.4
diff -u -p -r1.4.46.1 -r1.4
--- include/linux/mca.h 23 May 2004 23:31:15 -0000 1.4.46.1
+++ include/linux/mca.h 8 Oct 2003 20:53:03 -0000 1.4
@@ -12,7 +12,9 @@
#include <linux/device.h>
/* get the platform specific defines */
+#ifdef CONFIG_MCA
#include <asm/mca.h>
+#endif
/* The detection of MCA bus is done in the real mode (using BIOS).
* The information is exported to the protected code, where this
Any use?
--
"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-05-26 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 2:32 ahc1542 fun Jeff Garzik
2004-05-26 6:44 ` hch
2004-05-26 17:52 ` Matthew Wilcox [this message]
2004-05-27 17:30 ` Jeff Garzik
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=20040526175217.GU29154@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--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