| 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
| ||
|
Message-ID: <alpine.LNX.2.00.1106201552420.11049@pobox.suse.cz> Date: Mon, 20 Jun 2011 16:02:31 +0200 (CEST) From: Jiri Kosina <jkosina@...e.cz> To: Jonathan Neuschäfer <j.neuschaefer@....net> Cc: Rusty Russell <rusty@...tcorp.com.au>, linux-kernel@...r.kernel.org Subject: Re: [PATCH trivial] stop_machine.h: "disables preeempt" -> "disables preemption" On Sun, 19 Jun 2011, Jonathan Neuschäfer wrote: > Use the noun instead of a misspelled verb. > > Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@....net> > --- > include/linux/stop_machine.h | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/include/linux/stop_machine.h b/include/linux/stop_machine.h > index 092dc9b..2d3f0b1 100644 > --- a/include/linux/stop_machine.h > +++ b/include/linux/stop_machine.h > @@ -94,7 +94,7 @@ static inline int try_stop_cpus(const struct cpumask *cpumask, > * stop_machine "Bogolock": stop the entire machine, disable > * interrupts. This is a very heavy lock, which is equivalent to > * grabbing every spinlock (and more). So the "read" side to such a > - * lock is anything which disables preeempt. > + * lock is anything which disables preemption. If there wouldn't be the typo, I'd gladly keep the old version there. But with the typo being there anyway ... applied. -- Jiri Kosina SUSE Labs -- 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