From: linux@roeck-us•net (Guenter Roeck)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH omap v2 0/6] Fix OMAP uses of RCU from idle loop
Date: Wed, 18 May 2016 07:38:39 -0700 [thread overview]
Message-ID: <573C7E6F.90001@roeck-us.net> (raw)
In-Reply-To: <20160516184844.GA20144@linux.vnet.ibm.com>
On 05/16/2016 11:48 AM, Paul E. McKenney wrote:
> 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.
>
For the series, on top of mainline (which now experiences the problem fixed
by this series):
Tested-by: Guenter Roeck <linux@roeck-us•net>
Guenter
next prev parent reply other threads:[~2016-05-18 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 18:48 [PATCH omap v2 0/6] Fix OMAP uses of RCU from idle loop Paul E. McKenney
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-18 15:24 ` Mason
2016-05-18 17:31 ` 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 ` Guenter Roeck [this message]
2016-05-18 18:56 ` [PATCH omap v2 0/6] Fix OMAP uses of RCU from idle loop 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=573C7E6F.90001@roeck-us.net \
--to=linux@roeck-us$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/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