From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 4/5] clockevents: Add generic timer broadcast function
Date: Tue, 18 Dec 2012 14:17:13 -0800 [thread overview]
Message-ID: <50D0EB69.10901@codeaurora.org> (raw)
In-Reply-To: <1355832418-31692-5-git-send-email-mark.rutland@arm.com>
Minor nit
On 12/18/12 04:06, Mark Rutland wrote:
> diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
> index c2dd022..ec22a80 100644
> --- a/kernel/time/tick-broadcast.c
> +++ b/kernel/time/tick-broadcast.c
> @@ -86,6 +87,12 @@ int tick_is_broadcast_device(struct clock_event_device *dev)
> return (dev && tick_broadcast_device.evtdev == dev);
> }
>
> +static void err_broadcast(const struct cpumask *mask)
> +{
> + pr_crit_once("Attempted to broadcast tick, but no broadcast mechanism "
> + "present. Some CPUs may be unresponsive.");
This is missing a newline. You may also want to put the string on a
single line so we can easily grep for it in the sources.
> @@ -105,6 +112,14 @@ int tick_device_uses_broadcast(struct clock_event_device *dev, int cpu)
> */
> if (!tick_device_is_functional(dev)) {
> dev->event_handler = tick_handle_periodic;
> + if (!dev->broadcast)
> + dev->broadcast = tick_broadcast;
> + if (!dev->broadcast) {
> + pr_warn_once("%s depends on broadcast, but no "
> + "broadcast function available\n",
Same one line comment here. I thought checkpatch didn't complain anymore.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux@arm.linux.org.uk,
tglx@linutronix.de, nico@linaro.org, will.deacon@arm.com,
marc.zyngier@arm.com, john.stultz@linaro.org
Subject: Re: [RFC PATCH 4/5] clockevents: Add generic timer broadcast function
Date: Tue, 18 Dec 2012 14:17:13 -0800 [thread overview]
Message-ID: <50D0EB69.10901@codeaurora.org> (raw)
In-Reply-To: <1355832418-31692-5-git-send-email-mark.rutland@arm.com>
Minor nit
On 12/18/12 04:06, Mark Rutland wrote:
> diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
> index c2dd022..ec22a80 100644
> --- a/kernel/time/tick-broadcast.c
> +++ b/kernel/time/tick-broadcast.c
> @@ -86,6 +87,12 @@ int tick_is_broadcast_device(struct clock_event_device *dev)
> return (dev && tick_broadcast_device.evtdev == dev);
> }
>
> +static void err_broadcast(const struct cpumask *mask)
> +{
> + pr_crit_once("Attempted to broadcast tick, but no broadcast mechanism "
> + "present. Some CPUs may be unresponsive.");
This is missing a newline. You may also want to put the string on a
single line so we can easily grep for it in the sources.
> @@ -105,6 +112,14 @@ int tick_device_uses_broadcast(struct clock_event_device *dev, int cpu)
> */
> if (!tick_device_is_functional(dev)) {
> dev->event_handler = tick_handle_periodic;
> + if (!dev->broadcast)
> + dev->broadcast = tick_broadcast;
> + if (!dev->broadcast) {
> + pr_warn_once("%s depends on broadcast, but no "
> + "broadcast function available\n",
Same one line comment here. I thought checkpatch didn't complain anymore.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2012-12-18 22:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 12:06 [RFC PATCH 0/5] clockevents: decouple broadcast mechanism from drivers Mark Rutland
2012-12-18 12:06 ` Mark Rutland
2012-12-18 12:06 ` [RFC PATCH 1/5] ARM: remove useless guard in smp.c Mark Rutland
2012-12-18 12:06 ` Mark Rutland
2012-12-18 18:47 ` Stephen Boyd
2012-12-18 18:47 ` Stephen Boyd
2012-12-19 9:40 ` Mark Rutland
2012-12-19 9:40 ` Mark Rutland
2012-12-21 10:02 ` Santosh Shilimkar
2012-12-21 10:02 ` Santosh Shilimkar
2013-01-02 11:14 ` Mark Rutland
2013-01-02 11:14 ` Mark Rutland
2012-12-18 12:06 ` [RFC PATCH 2/5] clockevents: Add generic timer broadcast receiver Mark Rutland
2012-12-18 12:06 ` Mark Rutland
2012-12-18 22:17 ` Stephen Boyd
2012-12-18 22:17 ` Stephen Boyd
2012-12-19 10:19 ` Mark Rutland
2012-12-19 10:19 ` Mark Rutland
2012-12-21 10:02 ` Santosh Shilimkar
2012-12-21 10:02 ` Santosh Shilimkar
2013-01-02 10:59 ` Mark Rutland
2013-01-02 10:59 ` Mark Rutland
2012-12-18 12:06 ` [RFC PATCH 3/5] ARM: Use generic timer broadcast receive Mark Rutland
2012-12-18 12:06 ` Mark Rutland
2012-12-18 12:06 ` [RFC PATCH 4/5] clockevents: Add generic timer broadcast function Mark Rutland
2012-12-18 12:06 ` Mark Rutland
2012-12-18 22:17 ` Stephen Boyd [this message]
2012-12-18 22:17 ` Stephen Boyd
2012-12-19 10:37 ` Mark Rutland
2012-12-19 10:37 ` Mark Rutland
2012-12-18 12:06 ` [RFC PATCH 5/5] ARM: Add generic timer broadcast support Mark Rutland
2012-12-18 12:06 ` Mark Rutland
2012-12-21 10:08 ` [RFC PATCH 0/5] clockevents: decouple broadcast mechanism from drivers Santosh Shilimkar
2012-12-21 10:08 ` Santosh Shilimkar
2013-01-02 11:41 ` Mark Rutland
2013-01-02 11:41 ` Mark Rutland
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=50D0EB69.10901@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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.