From: javaman <javaman@katamail.com>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: [PATCH 2.5.x, 2.4.x ...] very small
Date: Fri, 21 Feb 2003 15:25:17 +0100 [thread overview]
Message-ID: <20030221144448Z267481-29901+571@vger.kernel.org> (raw)
A very small patch (my first patch :-) for Documentation/spinlocks.txt:
it replace "IFF" with "IF" ;-)
bye,
Paolo
--- Documentation/spinlocks.txt.orig Fri Feb 21 15:02:01 2003
+++ Documentation/spinlocks.txt Fri Feb 21 15:02:44 2003
@@ -136,7 +136,7 @@
If you have a case where you have to protect a data structure across
several CPU's and you want to use spinlocks you can potentially use
-cheaper versions of the spinlocks. IFF you know that the spinlocks are
+cheaper versions of the spinlocks. IF you know that the spinlocks are
never used in interrupt handlers, you can use the non-irq versions:
spin_lock(&lock);
next reply other threads:[~2003-02-21 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 14:25 javaman [this message]
2003-02-21 15:10 ` Murray J. Root
2003-02-21 15:16 ` Brian Gerst
2003-02-21 15:30 ` Dave Jones
2003-02-21 17:03 ` Steven Cole
[not found] <200302211454.h1LEsPh31866@neosilicon.transmeta.com>
2003-02-21 15:08 ` Linus Torvalds
2003-02-21 17:23 ` Paolo Ornati
2003-02-21 19:31 ` Thomas Molina
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=20030221144448Z267481-29901+571@vger.kernel.org \
--to=javaman@katamail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®