From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
kernel@agotnes.com, akpm@osdl.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-usb-users@lists.sourceforge.net,
linux-usb-devel@lists.sourceforge.net, stern@rowland.harvard.edu,
vsu@altlinux.ru
Subject: Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
Date: Wed, 28 Jun 2006 02:08:32 +0100 [thread overview]
Message-ID: <1151456912.2704.13.camel@localhost.portugal> (raw)
In-Reply-To: <1151024444.2858.14.camel@localhost.portugal>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
On Fri, 2006-06-23 at 02:00 +0100, Sergio Monteiro Basto wrote:
> On Thu, 2006-06-22 at 15:54 -0700, Chris Wedgwood wrote:
> > On Thu, Jun 22, 2006 at 11:46:38PM +0100, Sergio Monteiro Basto
> wrote:
> >
> > > yap, in my opinion this function should back to
> >
> > > +DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID,
> quirk_via_irq);
> >
> >
> > this is *obviousyl* wrong, it should never have been merged like
> that
> > and there are reports and complaints this causes problems for some
> > people
> >
>
> It was like that in kernel 2.6.16 and previous since, I don't know,
> 2.6.9 or 2.6.13 ....
Hi, Chris Wedgwood
I found the bugzilla report where the initial version of this function
quirk_via_irq (drivers/pci/quirks.c) has been made:
http://bugzilla.kernel.org/show_bug.cgi?id=3319#c28
might be interesting !
--
Sérgio M. B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-06-28 1:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 11:38 [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Johny Ågotnes
2006-06-20 11:21 ` Johny
2006-06-20 11:40 ` Andrew Morton
2006-06-20 13:22 ` Sergio Monteiro Basto
2006-06-21 10:50 ` Johny
2006-06-22 0:36 ` who I do know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]] Sergio Monteiro Basto
2006-06-22 0:47 ` Randy.Dunlap
2006-06-22 1:04 ` how I " Sergio Monteiro Basto
2006-06-22 4:08 ` Randy.Dunlap
2006-06-22 11:56 ` Sergio Monteiro Basto
2006-06-22 21:29 ` Randy.Dunlap
2006-06-22 22:46 ` Sergio Monteiro Basto
2006-06-22 22:54 ` Chris Wedgwood
2006-06-23 1:00 ` Sergio Monteiro Basto
2006-06-23 1:39 ` Randy.Dunlap
2006-06-23 1:50 ` Sergio Monteiro Basto
2006-06-23 2:02 ` Randy.Dunlap
2006-06-28 1:08 ` Sergio Monteiro Basto [this message]
2006-06-23 1:40 ` Johny
2006-06-22 23:25 ` Randy.Dunlap
2006-06-23 1:30 ` Sergio Monteiro Basto
2006-06-23 15:31 ` [linux-usb-devel] who I do " David Brownell
2006-06-20 12:09 ` [linux-usb-devel] [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Sergey Vlasov
2006-06-20 13:30 ` Sergio Monteiro Basto
2006-06-20 13:59 ` Sergey Vlasov
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=1151456912.2704.13.camel@localhost.portugal \
--to=sergio@sergiomb.no-ip.org \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=kernel@agotnes.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=rdunlap@xenotime.net \
--cc=stern@rowland.harvard.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox