From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: mmotm 2009-06-30-12-50 uploaded
Date: Thu, 02 Jul 2009 16:21:05 -0400 [thread overview]
Message-ID: <30563.1246566065@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 02 Jul 2009 12:47:26 PDT." <20090702124726.a253f13d.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Thu, 02 Jul 2009 12:47:26 PDT, Andrew Morton said:
> apart from having a crappy title, linux-next's
>
> : commit f29876421ec11f7d66f3d982219ef3af9bcccf32
> : Author: Rusty Russell <rusty@rustcorp.com.au>
> : AuthorDate: Wed Jul 1 12:37:19 2009 +1000
> : Commit: Stephen Rothwell <sfr@canb.auug.org.au>
> : CommitDate: Wed Jul 1 12:37:19 2009 +1000
> :
> : misc:work_on_cpu-acpi
> :
>
> causes get_throttling() to newly be called from an IPI, and lockdep doesn't
> like irq-disabled interrupt handlers doing local_irq_enable().
>
>
> If we rely upon these functions only ever being called from
> smp_call_function_single(), and if smp_call_function_single() is
> correctly implemented, we should be able to do this:
I'll take a leap of faith on the "correctly implemented" part. However,
I admit I'm probably going to wait till Len or somebody agrees on the
"only calledf from function_single()" part being correct before test-driving
the patch...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-07-02 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906301951.n5UJpUSY013305@imap1.linux-foundation.org>
[not found] ` <6719.1246562163@turing-police.cc.vt.edu>
2009-07-02 19:47 ` mmotm 2009-06-30-12-50 uploaded Andrew Morton
2009-07-02 20:21 ` Valdis.Kletnieks [this message]
2009-07-03 10:25 ` Valdis.Kletnieks
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=30563.1246566065@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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