One of the comments in tick_handle_periodic() had 'when' instead of 'which' (My guess :)). Fix it.
Signed-off-by: Viresh Kumar viresh.kumar@linaro.org --- kernel/time/tick-common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c index 20b2fe3..791a3a2 100644 --- a/kernel/time/tick-common.c +++ b/kernel/time/tick-common.c @@ -118,7 +118,7 @@ void tick_handle_periodic(struct clock_event_device *dev) * to be sure we're using a real hardware clocksource. * Otherwise we could get trapped in an infinite * loop, as the tick_periodic() increments jiffies, - * when then will increment time, posibly causing + * which then will increment time, posibly causing * the loop to trigger again and again. */ if (timekeeping_valid_for_hres())
On Tue, Mar 25, 2014 at 11:32 AM, Viresh Kumar viresh.kumar@linaro.org wrote:
One of the comments in tick_handle_periodic() had 'when' instead of 'which' (My guess :)). Fix it.
Signed-off-by: Viresh Kumar viresh.kumar@linaro.org
kernel/time/tick-common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c index 20b2fe3..791a3a2 100644 --- a/kernel/time/tick-common.c +++ b/kernel/time/tick-common.c @@ -118,7 +118,7 @@ void tick_handle_periodic(struct clock_event_device *dev) * to be sure we're using a real hardware clocksource. * Otherwise we could get trapped in an infinite * loop, as the tick_periodic() increments jiffies,
* when then will increment time, posibly causing
* which then will increment time, posibly causing
Also, on the same line s/posibly/possibly
Stratos
On 25 March 2014 16:05, Stratos Karafotis skarafotis@gmail.com wrote:
Also, on the same line s/posibly/possibly
Can't believe I missed that :)
Sent V2.
linaro-kernel@lists.linaro.org
-
Stratos Karafotis -
Viresh Kumar