public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead•org>
To: Andi Kleen <andi@firstfloor•org>
Cc: Len Brown <lenb@kernel•org>,
	Andrew Morton <akpm@linux-foundation•org>,
	randy.dunlap@oracle•com, linux-acpi@vger•kernel.org,
	linux-next@vger•kernel.org, Ingo Molnar <mingo@elte•hu>
Subject: Re: [PATCH -next] acpi utmisc: use WARN_ON() instead of warn_on_slowpath()
Date: Mon, 7 Jul 2008 00:03:20 -0700	[thread overview]
Message-ID: <20080707000320.25341603@infradead.org> (raw)
In-Reply-To: <4871B55C.7040009@firstfloor.org>

On Mon, 07 Jul 2008 08:19:08 +0200
Andi Kleen <andi@firstfloor•org> wrote:

> I'm dropping the ACPI part because we're getting too many
> reports of scary looking backtraces and ACPI exceptions are actually
> not that exceptional.

when I talked to Len about it he implied/said that these would only
happen for ACPI code bugs (and not bios bugs). Maybe he was
overestimating what the code would actually do; if so it would imo be
well worth splitting out ACPI code assertions versions things that are
BIOS caused (if only to be able to inform the user more consistently)


-- 
If you want to reach me at my work email, use arjan@linux•intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-07-07  7:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080701103339.b5acc1f3.randy.dunlap@oracle.com>
     [not found] ` <20080701131714.5093fa49.akpm@linux-foundation.org>
     [not found]   ` <23433248.1214943818230.JavaMail.oracle@acsmt302.oracle.com>
     [not found]     ` <20080701133535.f92a673c.akpm@linux-foundation.org>
2008-07-02 18:28       ` [PATCH -next] acpi utmisc: use WARN_ON() instead of warn_on_slowpath() Randy Dunlap
2008-07-02 18:50         ` Andi Kleen
2008-07-02 19:14           ` Andrew Morton
2008-07-02 19:31             ` Andi Kleen
2008-07-02 19:43               ` Andrew Morton
2008-07-02 20:11                 ` Andi Kleen
2008-07-02 20:35                   ` Andrew Morton
2008-07-02 20:51                     ` Andi Kleen
2008-07-02 21:02                       ` Andrew Morton
2008-07-02 21:07                         ` Andi Kleen
2008-07-02 21:14                           ` Andrew Morton
2008-07-06 17:18                             ` Len Brown
2008-07-06 18:13                               ` Andi Kleen
2008-07-06 18:52                               ` Arjan van de Ven
2008-07-07  6:19                                 ` Andi Kleen
2008-07-07  7:03                                   ` Arjan van de Ven [this message]
2008-07-08 15:44                                     ` Thomas Renninger

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=20080707000320.25341603@infradead.org \
    --to=arjan@infradead$(echo .)org \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=andi@firstfloor$(echo .)org \
    --cc=lenb@kernel$(echo .)org \
    --cc=linux-acpi@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    --cc=randy.dunlap@oracle$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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