public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Wilco Beekhuizen <wilcobeekhuizen@gmail.com>
Cc: Dave Jones <davej@redhat.com>,
	Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: VIA IRQ quirk missing PCI ids since 2.6.16.17
Date: Wed, 08 Nov 2006 15:19:08 +0000	[thread overview]
Message-ID: <1162999148.23956.8.camel@localhost.localdomain> (raw)
In-Reply-To: <6c4c86470611080054r21f5c632u674da23bf3d1cc32@mail.gmail.com>

Ar Mer, 2006-11-08 am 09:54 +0100, ysgrifennodd Wilco Beekhuizen:
> Why was this changed in the stable kernel anyway, especially in a
> micro-stability update? It seems to me it breaks more than it fixes.

Because it suffered from an acute case of being wrong. The blanket patch
proposed by Sergio is also wrong. Both break valid correct and working
systems while fixing some others.

The draft patch I posted fixes up precisely the right devices on
precisely the right bridges and nothing else which should mean we now
have a patch that gets all cases right.


  parent reply	other threads:[~2006-11-08 15:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 11:38 VIA IRQ quirk missing PCI ids since 2.6.16.17 Wilco Beekhuizen
2006-11-06 12:47 ` Sergio Monteiro Basto
2006-11-06 21:13   ` Alan Cox
2006-11-07  1:25     ` Dave Jones
2006-11-07  1:34       ` Alan Cox
2006-11-08  8:54         ` Wilco Beekhuizen
2006-11-08 12:43           ` Sergio Monteiro Basto
2006-11-08 14:55             ` Wilco Beekhuizen
2006-11-08 15:19           ` Alan Cox [this message]
2006-11-07  4:07       ` Greg KH
2006-11-07  8:31       ` Jeff Garzik
2006-11-08 17:22     ` Sergey Vlasov
2006-11-08 18:05       ` Alan Cox
2006-11-08 20:33         ` Sergey Vlasov
2006-11-06 13:30 ` Alan Cox

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=1162999148.23956.8.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergio@sergiomb.no-ip.org \
    --cc=wilcobeekhuizen@gmail.com \
    /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