public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Stian Jordet <liste@jordet.net>
Cc: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	akpm@osdl.org, torvalds@osdl.org, jeff@garzik.org,
	greg@kroah.com, cw@f00f.org, bjorn.helgaas@hp.com,
	linux-kernel@vger.kernel.org, harmon@ksu.edu,
	len.brown@intel.com, vsu@altlinux.ru
Subject: Re: [PATCH V3] VIA IRQ quirk behaviour change
Date: Mon, 11 Sep 2006 17:54:02 -0400	[thread overview]
Message-ID: <4505DAFA.20802@gentoo.org> (raw)
In-Reply-To: <1158005769.4748.0.camel@localhost.localdomain>

Stian Jordet wrote:
>> if it is , was resolved with this [PATCH V3] VIA IRQ quirk behaviour change ? 
> 
> I have no idea what you mean here, but it's by no means fixed by that
> patch, actually it just got worse (usb didn't work, but still got
> interrupts from eth0 - and it still used irq 11)

Are you sure? The failure report you sent me was from V2 of the patch. 
V3 should work fine, based on earlier comments and info from you.

Daniel

  parent reply	other threads:[~2006-09-11 21:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 22:33 [PATCH V3] VIA IRQ quirk behaviour change Daniel Drake
2006-09-09 14:20 ` Alan Cox
2006-09-09 14:44   ` Daniel Drake
2006-09-09 16:03     ` Alan Cox
2006-09-09 21:34       ` Daniel Drake
2006-09-10  0:31         ` Alan Cox
2006-09-10  0:21           ` Greg KH
2006-09-10  0:39             ` Chris Wedgwood
2006-09-10  4:37               ` Greg KH
2006-09-10  9:48                 ` Stian Jordet
2006-09-10 15:48             ` Daniel Drake
2006-09-10 18:40             ` Lee Revell
2006-09-10 20:45               ` Matthew Garrett
2006-09-10 21:30                 ` Lee Revell
2006-09-10 21:34                   ` Matthew Garrett
2006-09-19 20:04                 ` Lee Revell
2006-09-19 20:12                   ` Matthew Garrett
2006-09-19 20:28                     ` Lee Revell
2006-09-10 16:01           ` Daniel Drake
2006-09-10 16:39             ` Alan Cox
2006-09-10 16:44               ` Jeff Garzik
2006-09-10 19:06               ` Daniel Drake
2006-09-10 19:41                 ` Alan Cox
2006-09-10 19:21                   ` Stian Jordet
2006-09-11 15:33                     ` Sergio Monteiro Basto
2006-09-11 20:16                       ` Stian Jordet
2006-09-11 21:23                         ` Sergio Monteiro Basto
2006-09-11 21:38                           ` Stian Jordet
2006-09-12 12:37                             ` Sergio Monteiro Basto
2006-09-12 21:38                               ` Stian Jordet
2006-09-13  0:48                                 ` Sergio Monteiro Basto
2006-09-11 21:54                         ` Daniel Drake [this message]
2006-09-12  6:21                           ` Stian Jordet
2006-09-11 21:44                       ` Daniel Drake

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=4505DAFA.20802@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bjorn.helgaas@hp.com \
    --cc=cw@f00f.org \
    --cc=greg@kroah.com \
    --cc=harmon@ksu.edu \
    --cc=jeff@garzik.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liste@jordet.net \
    --cc=sergio@sergiomb.no-ip.org \
    --cc=torvalds@osdl.org \
    --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