From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Stefan Assmann <sassmann@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Beulich <JBeulich@novell.com>, Takashi Iwai <tiwai@suse.de>,
Junio C Hamano <gitster@pobox.com>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: lost parts of "pci, acpi: reroute PCI interrupt to legacy boot interrupt equivalent" during merge
Date: Wed, 20 Oct 2010 12:14:02 -0600 [thread overview]
Message-ID: <201010201214.03363.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <4CBF1896.70901@redhat.com>
On Wednesday, October 20, 2010 10:28:06 am Stefan Assmann wrote:
> Let me take a look at the current situation and see if I can come up
> with a solution. Sorry if things got messy.
When you redo this, can you update the printks to use dev_info()
and "[%04x:%04x]" for vendor/device, like the rest of PCI?
Actually, the bridge_has_boot_interrupt_variant() printk looks
superfluous to me.
Do you know how Windows handles these machines? I'm just wondering
if there's some ACPI or other information from the BIOS that we're
not handling quite correctly, and if we fixed that maybe we wouldn't
need a quirk.
ISTR a paper or some kind of writeup you did, but the commit
(e1d3a90846) doesn't mention it. Am I mis-remembering that?
It'd be kind of nice for archaeologists like me if there were a
kernel bugzilla with before/after dmesg logs and stuff.
Bjorn
next prev parent reply other threads:[~2010-10-20 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 10:03 lost parts of "pci, acpi: reroute PCI interrupt to legacy boot interrupt equivalent" during merge Jan Beulich
2010-10-20 13:48 ` Ingo Molnar
2010-10-20 15:15 ` Linus Torvalds
2010-10-20 15:24 ` Ingo Molnar
2010-10-20 16:28 ` Stefan Assmann
2010-10-20 18:14 ` Bjorn Helgaas [this message]
2010-10-20 19:54 ` Stefan Assmann
2010-10-20 21:31 ` Bjorn Helgaas
2010-10-21 18:20 ` Olaf Dabrunz
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=201010201214.03363.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=JBeulich@novell.com \
--cc=gitster@pobox.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sassmann@redhat.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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