From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-clk@vger.kernel.org
Cc: tony@atomide.com, mingo@kernel.org, linux@roeck-us.net,
rostedt@goodmis.org
Subject: [PATCH omap v2 0/6] Fix OMAP uses of RCU from idle loop
Date: Mon, 16 May 2016 11:48:44 -0700 [thread overview]
Message-ID: <20160516184844.GA20144@linux.vnet.ibm.com> (raw)
Hello!
The following series fixes a number of uses of RCU from the idle loop.
These are all due to tracing, so the fix is simply to append _rcuidle
to the event-tracing call.
Changes since v1: Fix commit-log subjects and add maintainers on CC.
Thanx, Paul
------------------------------------------------------------------------
arch/arm/kernel/smp.c | 2 +-
arch/arm/mach-omap2/powerdomain.c | 9 +++++----
drivers/base/power/runtime.c | 14 +++++++-------
drivers/clk/clk.c | 8 ++++----
4 files changed, 17 insertions(+), 16 deletions(-)
next reply other threads:[~2016-05-16 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 18:48 Paul E. McKenney [this message]
2016-05-16 18:50 ` [PATCH v2 omap 1/6] arm: Use _rcuidle tracepoint to allow use from idle Paul E. McKenney
2016-05-16 18:50 ` [PATCH v2 omap 2/6] arm: Use _rcuidle for suspend/resume tracepoints Paul E. McKenney
2016-05-16 18:50 ` [PATCH v2 omap 3/6] arm: Add _rcuidle tracepoints to allow clk_core_disable() use from idle Paul E. McKenney
2016-05-16 18:50 ` [PATCH v2 omap 4/6] arm: Add _rcuidle suffix to allow rpm_idle() " Paul E. McKenney
2016-05-16 18:50 ` [PATCH v2 omap 5/6] arm: Add _rcuidle suffix to allow rpm_resume() to be called " Paul E. McKenney
2016-05-16 18:50 ` [PATCH v2 omap 6/6] arm: Use _rcuidle suffix to allow clk_core_enable() to used " Paul E. McKenney
2016-05-18 14:38 ` [PATCH omap v2 0/6] Fix OMAP uses of RCU from idle loop Guenter Roeck
2016-05-18 18:56 ` Paul E. McKenney
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=20160516184844.GA20144@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--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;
as well as URLs for NNTP newsgroup(s).