From: Andrew de Quincey <adq_dvb@lidskialf.net>
To: Andrew Morton <akpm@osdl.org>
Cc: al.rau@gmx.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI patch which fixes all my IRQ problems on nforce2 -- linux-2.5.75-acpi-irqparams-final4.patch
Date: Mon, 28 Jul 2003 21:26:30 +0100 [thread overview]
Message-ID: <200307282126.30584.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <20030728125152.4a185090.akpm@osdl.org>
> I fixed this in test2-mm1: it needs a
>
> ACPI_FUNCTION_TRACE("acpi_pci_link_allocate");
>
> at the start of that function.
>
> I made a bunch of other changes to that patch - mainly whitespace fixups.
> It is at
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test2/2
>.6.0-test2-mm1/broken-out/nforce2-acpi-fixes.patch
Great, thanks.
> I'm thinking that perhaps io_apic_irq_read_proc() and print_IO_APIC()
> should be consolidated.
I agree. I was going to fix that problem in a later patch; this one is already
changing a little too much in one go for my liking.
next prev parent reply other threads:[~2003-07-28 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 22:05 [PATCH] ACPI patch which fixes all my IRQ problems on nforce2 -- linux-2.5.75-acpi-irqparams-final4.patch Andrew de Quincey
2003-07-28 15:30 ` Alexander Rau
2003-07-28 15:38 ` Andrew de Quincey
[not found] ` <3F2546EF.9030803@gmx.de>
[not found] ` <200307281653.58216.adq_dvb@lidskialf.net>
2003-07-28 16:25 ` Alexander Rau
2003-07-28 20:57 ` Alexander Rau
2003-07-28 21:16 ` Andrew de Quincey
2003-07-29 8:46 ` Thomas Schlichter
2003-07-28 19:51 ` Andrew Morton
2003-07-28 20:26 ` Andrew de Quincey [this message]
2003-07-28 15:42 ` Compile error with 2.6.0-test2 config attached lkml
2003-07-28 15:53 ` [PATCH] ACPI patch which fixes all my IRQ problems on nforce2 -- linux-2.6.0-test2-acpi-irqparams-final5.patch Andrew de Quincey
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=200307282126.30584.adq_dvb@lidskialf.net \
--to=adq_dvb@lidskialf.net \
--cc=akpm@osdl.org \
--cc=al.rau@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).