From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Daniel Drake <dsd@gentoo.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: Mon, 11 Dec 2006 01:42:48 +0000 [thread overview]
Message-ID: <1165801368.2987.20.camel@monteirov> (raw)
In-Reply-To: <20061210160053.GD10351@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On Sun, 2006-12-10 at 17:00 +0100, Adrian Bunk wrote:
> +DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID,
> quirk_via_irq);
This is back to state of kernel 2.6.16 final (without .x)
In kernel 2.6.17 final we got
(http://lkml.org/lkml/2006/4/19/16)
commit 75cf7456dd87335f574dcd53c4ae616a2ad71a11
Author: Chris Wedgwood <cw@f00f.org>
Date: Tue Apr 18 23:57:09 2006 -0700
Signed-off-by: Chris Wedgwood <cw@f00f.org>
Acked-by: Jeff Garzik <jeff@garzik.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
and
commit a7b862f663d81858531dfccc0537bc9d8a2a4121
Author: Chris Wedgwood <cw@f00f.org>
Date: Mon May 15 09:43:55 2006 -0700
[PATCH] VIA quirk fixup, additional PCI IDs
BUT the latest stable and tested patch is the commit 09d6029f43ebbe7307854abdae204c25d711ff94
PCI: VIA IRQ quirk behaviour change, which in my opinion that should go in.
Thanks,
--
Sérgio M.B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-12-11 1:43 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
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 [this message]
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=1165801368.2987.20.camel@monteirov \
--to=sergio@sergiomb.no-ip.org \
--cc=bjdouma@xs4all.nl \
--cc=bjorn.helgaas@hp.com \
--cc=brice@myri.com \
--cc=bunk@stusta.de \
--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