From: Alan Cox <alan@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Daniel Drake <dsd@gentoo.org>, Alan Cox <alan@redhat.com>,
Chris Wedgwood <cw@f00f.org>, Daniel Ritz <daniel.ritz@gmx.ch>,
Jean Delvare <khali@linux-fr.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Linus Torvalds <torvalds@osdl.org>, Brice Goglin <brice@myri.com>,
"John W. Linville" <linville@tuxdriver.com>,
Bauke Jan Douma <bjdouma@xs4all.nl>,
Tomasz Koprowski <tomek@koprowski.org>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: RFC: PCI quirks update for 2.6.16
Date: Thu, 7 Dec 2006 11:37:03 -0500 [thread overview]
Message-ID: <20061207163703.GB16103@devserv.devel.redhat.com> (raw)
In-Reply-To: <20061207145755.GI8963@stusta.de>
On Thu, Dec 07, 2006 at 03:57:56PM +0100, Adrian Bunk wrote:
> Looking at Alan's patch in -mm, it seems the best current solution for
> 2.6.16 is to go back to the pre-2.6.16.17
> DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq);
> and revisit this after Alan's patch was released with 2.6.20?
If you want 2.6.16.* not to risk any reversions of good behaviour then I'd agree
I'm pretty sure the new code is right cool and wonderful *BUT* it may not be
of course and it may also break broken bioses differently 8(
next prev parent reply other threads:[~2006-12-07 16:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 13:24 RFC: PCI quirks update for 2.6.16 Adrian Bunk
2006-12-07 13:53 ` Sergey Vlasov
2006-12-07 17:27 ` Bauke Jan Douma
2006-12-07 18:32 ` Sergey Vlasov
2006-12-08 15:34 ` Adrian Bunk
2006-12-07 14:38 ` Daniel Drake
2006-12-07 14:57 ` Adrian Bunk
2006-12-07 16:37 ` Alan Cox [this message]
2006-12-10 4:09 ` Sergio Monteiro Basto
2006-12-10 16:00 ` Adrian Bunk
2006-12-10 16:22 ` Daniel Drake
2006-12-10 22:33 ` Chris Wedgwood
2006-12-10 22:39 ` Linus Torvalds
2006-12-10 22:49 ` Chris Wedgwood
2006-12-11 1:17 ` Linus Torvalds
2006-12-10 23:47 ` Adrian Bunk
2006-12-11 1:23 ` Linus Torvalds
2006-12-11 12:52 ` Adrian Bunk
2006-12-19 6:08 ` Sergio Monteiro Basto
2006-12-11 1:42 ` Sergio Monteiro Basto
2006-12-11 12:41 ` Adrian Bunk
2006-12-11 12:48 ` Sergio Monteiro Basto
2006-12-11 13:01 ` Adrian Bunk
2006-12-07 19:54 ` Jean Delvare
2006-12-07 20:45 ` Tomek Koprowski
2006-12-08 15:42 ` Adrian Bunk
2006-12-08 16:11 ` RFC: PCI quirks update for 2.6.16 (v2) Adrian Bunk
2006-12-08 21:02 ` RFC: PCI quirks update for 2.6.16 Brice Goglin
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=20061207163703.GB16103@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=bjdouma@xs4all.nl \
--cc=bjorn.helgaas@hp.com \
--cc=brice@myri.com \
--cc=bunk@stusta.de \
--cc=cw@f00f.org \
--cc=daniel.ritz@gmx.ch \
--cc=dsd@gentoo.org \
--cc=gregkh@suse.de \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linville@tuxdriver.com \
--cc=tomek@koprowski.org \
--cc=torvalds@osdl.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