mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: Kimball Murray <kimball.murray@gmail.com>,
	linux-kernel@vger.kernel.org, akpm@digeo.com, ak@suse.de,
	kmurray@redhat.com, natalie.protasevich@unisys.com,
	linux-acpi@vger.kernel.org
Subject: RE: [(repost) git Patch 1/1] avoid IRQ0 ioapic pin collision
Date: Wed, 26 Apr 2006 13:58:24 +0100	[thread overview]
Message-ID: <1146056305.5155.24.camel@bastov.localdomain> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB6466487@hdsmsx411.amr.corp.intel.com>

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

I think, it is about time, not thinking via quirks as workarounds,
because all pcis (on via) are quirked, some are quirked twice.
And we should think in programmer interrupts of via chipset, in specific
function for this propose, for me, doesn't make sense every time VIA put
other ID out, we have to add quirks to this ID , as this was an
exception. 

Thanks, 


On Tue, 2006-04-25 at 15:53 -0400, Brown, Len wrote:
> I'd rather see the original irq-renaming patch
> and its subsequent multiple via workaround patches
> reverted than to further complicate what is becoming
> a fragile mess.
> 
> -Len
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Sérgio M.B.

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

  reply	other threads:[~2006-04-26 12:58 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 19:53 Brown, Len
2006-04-26 12:58 ` Sergio Monteiro Basto [this message]
2006-04-26 13:17 ` Andi Kleen
2006-04-26 13:56   ` Kimball Murray
2006-04-26 14:01     ` Kimball Murray
  -- strict thread matches above, loose matches on Subject: below --
2006-05-09  5:14 Protasevich, Natalie
2006-05-09  4:25 Brown, Len
2006-05-09  3:10 Protasevich, Natalie
2006-05-08 21:51 Brown, Len
2006-05-08 18:37 Protasevich, Natalie
2006-05-06  6:42 Protasevich, Natalie
2006-05-06  6:18 Brown, Len
2006-05-04 16:42 Protasevich, Natalie
2006-05-04 16:04 Brown, Len
2006-05-04 22:41 ` Eric W. Biederman
2006-05-04 15:33 Brown, Len
2006-05-04  5:07 Brown, Len
2006-05-04 15:31 ` Eric W. Biederman
2006-05-02 23:52 Protasevich, Natalie
2006-05-02  7:41 Brown, Len
2006-05-02  7:46 ` Andi Kleen
2006-05-02  8:33 ` Eric W. Biederman
2006-05-01 23:21 Brown, Len
2006-05-02  6:14 ` Andi Kleen
2006-05-02  6:57   ` Eric W. Biederman
2006-05-02  7:11     ` Andi Kleen
2006-05-02  7:39       ` Eric W. Biederman
2006-05-02  6:24 ` Eric W. Biederman
2006-04-27 20:36 Protasevich, Natalie
2006-04-30 23:17 ` Eric W. Biederman
2006-04-27 19:32 Brown, Len
2006-04-27 19:26 Protasevich, Natalie
2006-04-27 19:10 Protasevich, Natalie
2006-04-27 19:13 ` Andi Kleen
2006-04-27 18:13 Brown, Len
2006-04-27 18:16 ` Andi Kleen
2006-04-26 14:00 Protasevich, Natalie
2006-04-25 16:06 Kimball Murray
2006-04-26 11:27 ` Andi Kleen

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=1146056305.5155.24.camel@bastov.localdomain \
    --to=sergio@sergiomb.no-ip.org \
    --cc=ak@suse.de \
    --cc=akpm@digeo.com \
    --cc=kimball.murray@gmail.com \
    --cc=kmurray@redhat.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natalie.protasevich@unisys.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

all inboxes | Powered by JetHome®