| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 25 Mar 2014 12:35:55 +0200 From: Stratos Karafotis <skarafotis@...il.com> To: Viresh Kumar <viresh.kumar@...aro.org> Cc: tglx@...utronix.de, linaro-kernel@...ts.linaro.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] tick: fix spelling mistake in tick_handle_periodic() On Tue, Mar 25, 2014 at 11:32 AM, Viresh Kumar <viresh.kumar@...aro.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@...aro.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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists