From: Jean Delvare <jdelvare@suse.de>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Sergey Vlasov <vsu@altlinux.ru>,
Daniel Drake <dsd@reactivated.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] VIA IRQ quirk breakage fix
Date: Tue, 30 Jan 2007 17:17:08 +0100 [thread overview]
Message-ID: <200701301717.08792.jdelvare@suse.de> (raw)
In-Reply-To: <20070130162151.2a0e8bf1@localhost.localdomain>
Le Mardi 30 Janvier 2007 17:21, Alan a écrit :
> On Tue, 30 Jan 2007 14:49:51 +0100 Jean Delvare wrote:
> > I do believe this is 2.6.20 material. Given that Alan's version doesn't
> > work _at all_, my patch can only help. The real regression is between
> > 2.6.19 and the current Linus tree (with Alan's quirk.)
>
> I believe my version works for all but the 686B
It would if pci_find_present() was working at quirk time, which apparently
isn't the case in Linus' tree. And the bug report I received was on a VT8233.
--
Jean Delvare
Suse L3
next prev parent reply other threads:[~2007-01-30 16:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 0:33 via irq quirk breakage Nick Piggin
2007-01-29 15:00 ` Jean Delvare
2007-01-29 15:51 ` Alan
2007-01-30 12:29 ` Jean Delvare
2007-01-30 16:05 ` Alan
2007-01-30 2:35 ` Nick Piggin
2007-01-30 7:54 ` Jean Delvare
2007-01-30 8:32 ` Nick Piggin
2007-01-30 11:47 ` Sergey Vlasov
2007-01-30 12:25 ` [PATCH] VIA IRQ quirk breakage fix Jean Delvare
2007-01-30 13:38 ` Nick Piggin
2007-01-30 13:49 ` Jean Delvare
2007-01-30 16:21 ` Alan
2007-01-30 16:17 ` Jean Delvare [this message]
2007-01-30 18:02 ` Andrew Morton
2007-01-31 2:37 ` Andrew Morton
2007-02-01 7:39 ` Jean Delvare
2007-01-30 14:56 ` via irq quirk breakage Alan
2007-01-30 14:50 ` Jeff Garzik
2007-01-30 14:25 ` Alan
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=200701301717.08792.jdelvare@suse.de \
--to=jdelvare@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=dsd@reactivated.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=vsu@altlinux.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.