From: kuebelr@email.uc.edu
To: torvalds@transmeta.com, marcelo@conectiva.com.br
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] spelling mistakes
Date: Tue, 23 Apr 2002 15:50:52 -0400 [thread overview]
Message-ID: <20020423195052.GA967@cartman> (raw)
Fixes a few spelling mistakes in documentation (arch/i386/boot/setup.S,
Documentation/sysrq.txt). Pretty boring. This is against 2.4.19-pre7,
but also applies to 2.5.9.
Thanks.
Rob.
diff -Naur linux-2.4/Documentation/sysrq.txt linux-2.4-work/Documentation/sysrq.txt
--- linux-2.4/Documentation/sysrq.txt Tue Sep 18 01:52:35 2001
+++ linux-2.4-work/Documentation/sysrq.txt Tue Apr 23 10:55:44 2002
@@ -153,7 +153,7 @@
and 4 functions are exported for interface to it: __sysrq_lock_table,
__sysrq_unlock_table, __sysrq_get_key_op, and __sysrq_put_key_op. The
functions __sysrq_swap_key_ops and __sysrq_swap_key_ops_nolock are defined
-in the header itself, and the REGISTER and UNREGISTER macros are built fromi
+in the header itself, and the REGISTER and UNREGISTER macros are built from
these. More complex (and dangerous!) manipulations of the table are possible
using these functions, but you must be careful to always lock the table before
you read or write from it, and to unlock it again when you are done. (And of
diff -Naur linux-2.4/arch/i386/boot/setup.S linux-2.4-work/arch/i386/boot/setup.S
--- linux-2.4/arch/i386/boot/setup.S Mon Feb 25 14:37:52 2002
+++ linux-2.4-work/arch/i386/boot/setup.S Tue Apr 23 10:54:02 2002
@@ -805,7 +805,7 @@
#
# but we yet haven't reloaded the CS register, so the default size
# of the target offset still is 16 bit.
-# However, using an operant prefix (0x66), the CPU will properly
+# However, using an operand prefix (0x66), the CPU will properly
# take our 48 bit far pointer. (INTeL 80386 Programmer's Reference
# Manual, Mixing 16-bit and 32-bit code, page 16-6)
next reply other threads:[~2002-04-23 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 19:50 kuebelr [this message]
2002-04-29 3:28 ` [PATCH] spelling mistakes Rusty Russell
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=20020423195052.GA967@cartman \
--to=kuebelr@email.uc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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