public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Jörg Otte" <jrg.otte@googlemail.com>,
	"Andi Kleen" <ak@linux.intel.com>,
	linux-kernel@vger.kernel.org, "Len Brown" <lenb@kernel.org>
Subject: Re: [v3.4-rc1] ACPI regression bisected
Date: Thu, 12 Apr 2012 15:29:04 +0100	[thread overview]
Message-ID: <20120412142904.GA4130@srcf.ucam.org> (raw)
In-Reply-To: <alpine.LFD.2.02.1204121055200.2542@ionos>

On Thu, Apr 12, 2012 at 10:57:45AM +0200, Thomas Gleixner wrote:

> OK, so now the question is whether the ACPI interrupt can end up being
> shared or not.

Per spec:

"OSPM is required to treat the ACPI SCI interrupt as a sharable, level, 
active low interrupt."

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2012-04-12 14:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 15:05 [v3.4-rc1] ACPI regression bisected Jörg Otte
2012-04-02 23:54 ` Andi Kleen
2012-04-03  8:11   ` Thomas Gleixner
2012-04-12  8:35     ` Jörg Otte
2012-04-12  8:57       ` Thomas Gleixner
2012-04-12 11:42         ` Paul Bolle
2012-04-12 17:06           ` Thomas Gleixner
2012-04-12 21:52             ` Paul Bolle
2012-04-12 14:29         ` Matthew Garrett [this message]
2012-04-12 17:04           ` Thomas Gleixner
2012-04-12 17:09             ` Thomas Gleixner
2012-04-12 19:26               ` Andi Kleen
2012-04-12 20:42                 ` Thomas Gleixner
2012-04-18  9:25                   ` Paul Bolle
2012-04-18 10:29                     ` Thomas Gleixner
2012-04-18 11:07                       ` Paul Bolle
2012-04-18 17:24                       ` Linus Torvalds
2012-04-18 19:25                         ` Thomas Gleixner
2012-04-19  9:30                 ` Thomas Gleixner
2012-04-03  9:13   ` Jörg Otte

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=20120412142904.GA4130@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=ak@linux.intel.com \
    --cc=jrg.otte@googlemail.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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