From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
linux-next@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP systems
Date: Mon, 7 Jul 2008 01:02:37 +0200 [thread overview]
Message-ID: <200807070102.38854.rjw@sisk.pl> (raw)
In-Reply-To: <20080701202453.GD4896@elte.hu>
On Tuesday, 1 of July 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
>
> > On Tuesday, 1 of July 2008, Ingo Molnar wrote:
> > >
> > > * Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> > >
> > > > Assuming it works for Rafael (still haven't had time to pull my nx6125
> > > > out of storage):
> > > >
> > > > Signed-off-by: mjg@redhat.com
> > >
> > > Rafael, could you please try the latest tip/master that i've just pushed
> > > out:
> > >
> > > http://people.redhat.com/mingo/tip.git/README
> > >
> > > it has the final form of these changes integrated - it should in
> > > theory work out of box on your system, with no boot parameters or
> > > other explicit quirks needed anywhere.
> >
> > I tested patches [1/2] (your version) and [2/2] on top of today's
> > linux-next and they work just fine.
>
> thanks Rafael!
Well, I'm afraid that my information wasn't correct. The patches actually
don't work, but I had my own additional patch that fixed the problem applied,
which I've only just discovered. Sorry for the confusion and the issue is
still unfixed.
Thanks,
Rafael
next prev parent reply other threads:[~2008-07-06 23:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 0:12 [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP systems Maciej W. Rozycki
2008-07-01 0:17 ` Matthew Garrett
2008-07-01 8:46 ` Ingo Molnar
2008-07-01 19:58 ` Rafael J. Wysocki
2008-07-01 20:24 ` Ingo Molnar
2008-07-04 21:21 ` Rafael J. Wysocki
2008-07-06 23:02 ` Rafael J. Wysocki [this message]
2008-07-07 1:19 ` Rafael J. Wysocki
2008-07-07 7:17 ` Ingo Molnar
2008-07-07 7:36 ` Ingo Molnar
2008-07-07 12:24 ` Rafael J. Wysocki
2008-07-07 11:41 ` Maciej W. Rozycki
2008-07-07 12:23 ` Rafael J. Wysocki
2008-07-07 14:01 ` Maciej W. Rozycki
2008-07-07 18:03 ` Rafael J. Wysocki
2008-07-07 20:10 ` Maciej W. Rozycki
2008-07-07 20:31 ` Rafael J. Wysocki
2008-07-07 21:39 ` Maciej W. Rozycki
2008-07-07 22:10 ` Rafael J. Wysocki
2008-07-07 12:28 ` Rafael J. Wysocki
2008-07-07 17:10 ` Maciej W. Rozycki
2008-07-07 17:51 ` Ray Lee
2008-07-07 18:09 ` Rafael J. Wysocki
2008-07-07 19:59 ` Maciej W. Rozycki
2008-07-07 20:17 ` Rafael J. Wysocki
2008-07-07 21:38 ` Maciej W. Rozycki
2008-07-07 20:30 ` Maciej W. Rozycki
2008-07-07 3:54 ` Zhao Forrest
2008-07-07 12:34 ` Rafael J. Wysocki
2008-07-08 11:24 ` Andreas Herrmann
2008-07-08 14:39 ` Maciej W. Rozycki
2008-07-08 15:27 ` Rafael J. Wysocki
2008-07-08 16:25 ` Maciej W. Rozycki
2008-07-08 16:54 ` Rafael J. Wysocki
[not found] <fa.OuKI5CNmq3HqeBQCfWOUtrq4+oA@ifi.uio.no>
2008-07-03 5:44 ` Robert Hancock
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=200807070102.38854.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=tglx@linutronix.de \
/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).