public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Kimball Murray <kimball.murray@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@digeo.com, kmurray@redhat.com,
	natalie.protasevich@unisys.com, len.brown@intel.com,
	linux-acpi@vger.kernel.org
Subject: Re: [git Patch 1/1] avoid IRQ0 ioapic pin collision
Date: Fri, 21 Apr 2006 04:17:58 +0200	[thread overview]
Message-ID: <200604210417.59028.ak@suse.de> (raw)
In-Reply-To: <20060420230931.10317.38083.sendpatchset@dhcp83-97.boston.redhat.com>

On Friday 21 April 2006 01:14, Kimball Murray wrote:
> Hello!
> 
> I'm working on an x86_64 platfrom, where I've hit a problem that appears to
> be caused by a patch that went into 2.6.13 some time ago.  (git details are
> below).  Basically, that patch introduced a work-around for a VIA chipset
> limitation (only 4 bits to store a PCI interrupt).  And that work-around
> causes an unfortunate pin collision on our ioapic.


The patch looks reasonable except

- The variable should be __initdata
- The externs belong in headers

Actually I plan to garbage collect large parts of the x86-64 check_timer
RSN (basically I want to eliminate all the non ACPI compliant routing
support). That might simplify a bit. But I guess it would be still all 
needed for i386 anyways, so it's ok to have it.

-Andi

  reply	other threads:[~2006-04-21  2:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 23:14 [git Patch 1/1] avoid IRQ0 ioapic pin collision Kimball Murray
2006-04-21  2:17 ` Andi Kleen [this message]
2006-04-23  5:02 ` 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=200604210417.59028.ak@suse.de \
    --to=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