From: Kevin Hilman <khilman@kernel.org>
To: Jisheng Zhang <jszhang@marvell.com>
Cc: <tony@atomide.com>, <linux@arm.linux.org.uk>,
<linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: OMAP2+: PM: Denote the cpuidle tracepoints as _rcuidle()
Date: Wed, 23 Sep 2015 10:59:04 -0700 [thread overview]
Message-ID: <7hfv25dnkn.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1442554881-706-1-git-send-email-jszhang@marvell.com> (Jisheng Zhang's message of "Fri, 18 Sep 2015 13:41:21 +0800")
Jisheng Zhang <jszhang@marvell.com> writes:
> The cpuidle tracepoints are called within a rcu_idle_exit() section, and
> must be denoted with the _rcuidle() version of the tracepoint.
>
> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
Acked-by: Kevin Hilman <khilman@linaro.org>
next prev parent reply other threads:[~2015-09-23 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 5:41 [PATCH] ARM: OMAP2+: PM: Denote the cpuidle tracepoints as _rcuidle() Jisheng Zhang
2015-09-23 17:59 ` Kevin Hilman [this message]
2015-09-23 18:08 ` Tony Lindgren
2015-09-24 3:18 ` Jisheng Zhang
2015-10-12 23:10 ` Tony Lindgren
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=7hfv25dnkn.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox