From: Rusty Trivial Russell <rusty@rustcorp.com.au>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [TRIVIAL] fix documentation in include_asm-i386_bitops.h
Date: Fri, 08 Nov 2002 18:51:34 +1100 [thread overview]
Message-ID: <20021108081529.1BD922C37A@lists.samba.org> (raw)
From: "Vitezslav Samel" <samel@mail.cz>
Whean I was searching for prototype for set_bit() I found IMHO wrong doc
entries in include/asm-i386/bitops.h. Please consider applying.
Cheers,
Vita
--- trivial-2.5-bk/include/asm-i386/bitops.h.orig 2002-11-08 18:46:34.000000000 +1100
+++ trivial-2.5-bk/include/asm-i386/bitops.h 2002-11-08 18:46:34.000000000 +1100
@@ -89,7 +89,7 @@
/**
* __change_bit - Toggle a bit in memory
- * @nr: the bit to set
+ * @nr: the bit to change
* @addr: the address to start counting from
*
* Unlike change_bit(), this function is non-atomic and may be reordered.
@@ -106,7 +106,7 @@
/**
* change_bit - Toggle a bit in memory
- * @nr: Bit to clear
+ * @nr: Bit to change
* @addr: Address to start counting from
*
* change_bit() is atomic and may not be reordered.
@@ -162,7 +162,7 @@
/**
* test_and_clear_bit - Clear a bit and return its old value
- * @nr: Bit to set
+ * @nr: Bit to clear
* @addr: Address to count from
*
* This operation is atomic and cannot be reordered.
@@ -181,7 +181,7 @@
/**
* __test_and_clear_bit - Clear a bit and return its old value
- * @nr: Bit to set
+ * @nr: Bit to clear
* @addr: Address to count from
*
* This operation is non-atomic and can be reordered.
@@ -213,7 +213,7 @@
/**
* test_and_change_bit - Change a bit and return its new value
- * @nr: Bit to set
+ * @nr: Bit to change
* @addr: Address to count from
*
* This operation is atomic and cannot be reordered.
--
Don't blame me: the Monkey is driving
File: "Vitezslav Samel" <samel@mail.cz>: fix documentation in include_asm-i386_bitops.h
reply other threads:[~2002-11-08 8:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021108081529.1BD922C37A@lists.samba.org \
--to=rusty@rustcorp.com.au \
--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®