From: Kevin Hilman <khilman@ti.com>
To: NeilBrown <neilb@suse.de>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] omap: add rcu_locking to omap2_set_init_voltage.
Date: Mon, 09 Jan 2012 15:11:04 -0800 [thread overview]
Message-ID: <87obucxyif.fsf@ti.com> (raw)
In-Reply-To: <20120109131412.6238edf3@notabene.brown> (NeilBrown's message of "Mon, 9 Jan 2012 13:14:12 +1100")
NeilBrown <neilb@suse.de> writes:
> opp_find_freq_ceil and opp_get_voltage are documented as requiring
> rcu_lock to be held. So hold it.
>
> Signed-off-by: NeilBrown <neilb@suse.de>
Missing 'ARM: ' prefix, but I added it locally and queued as a fix for
v3.3.
Thanks for the patch!
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap: add rcu_locking to omap2_set_init_voltage.
Date: Mon, 09 Jan 2012 15:11:04 -0800 [thread overview]
Message-ID: <87obucxyif.fsf@ti.com> (raw)
In-Reply-To: <20120109131412.6238edf3@notabene.brown> (NeilBrown's message of "Mon, 9 Jan 2012 13:14:12 +1100")
NeilBrown <neilb@suse.de> writes:
> opp_find_freq_ceil and opp_get_voltage are documented as requiring
> rcu_lock to be held. So hold it.
>
> Signed-off-by: NeilBrown <neilb@suse.de>
Missing 'ARM: ' prefix, but I added it locally and queued as a fix for
v3.3.
Thanks for the patch!
Kevin
next prev parent reply other threads:[~2012-01-09 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 2:14 [PATCH] omap: add rcu_locking to omap2_set_init_voltage NeilBrown
2012-01-09 2:14 ` NeilBrown
2012-01-09 23:11 ` Kevin Hilman [this message]
2012-01-09 23:11 ` Kevin Hilman
2012-01-09 23:12 ` Kevin Hilman
2012-01-09 23:12 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2011-12-30 1:33 NeilBrown
2012-01-06 19:07 ` Kevin Hilman
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=87obucxyif.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.