mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Daniel Drake <dsd@gentoo.org>,
	linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] pci quirks: Sort out the VIA mess once and for all	(hopefully)
Date: Thu, 09 Nov 2006 01:18:13 +0000	[thread overview]
Message-ID: <1163035093.13988.9.camel@monteirov> (raw)
In-Reply-To: <1163018356.23956.88.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

First a salute to subject :) I hope so!

I will try the patch on my old laptop, which need the quirks, soon as
possible but I don't know if can be in this month.

On Wed, 2006-11-08 at 20:39 +0000, Alan Cox wrote:
> I think your patch is going to break stuff, without the patch will
> break more, 

My point of view is: The stuff was already breaked in kernels before
2.6.16. And the patch is a improvement from kernel 2.6.16. Not perfect,
we now.

> and hopefully this patch will not break anything - but there is risk.
> I think it's up to Linus what he wants to do for .19 

yap, it a risk because, drivers team tend to workaround the problems and
when we change IRQ routing, in this case correctly, workaround may blow
it.

Thanks,
-- 
Sérgio M.B.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]

  reply	other threads:[~2006-11-09  1:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 16:25 Alan Cox
2006-11-08 17:58 ` Jeff Garzik
2006-11-08 19:57 ` [PATCH] pci quirks: Sort out the VIA mess once and for all ?(hopefully) Luca Tettamanti
2006-11-08 20:04 ` [PATCH] pci quirks: Sort out the VIA mess once and for all (hopefully) Daniel Drake
2006-11-08 20:39   ` Alan Cox
2006-11-09  1:18     ` Sergio Monteiro Basto [this message]
2007-04-14 13:22       ` Sergio Monteiro Basto

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=1163035093.13988.9.camel@monteirov \
    --to=sergio@sergiomb.no-ip.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®