From: Miaohe Lin <linmiaohe@huawei.com>
To: <arnd@arndb.de>
Cc: <linux-arch@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linmiaohe@huawei.com>
Subject: [PATCH] locking/atomic/bitops: Fix some wrong param names in comments
Date: Thu, 10 Sep 2020 05:10:04 -0400 [thread overview]
Message-ID: <20200910091004.8921-1-linmiaohe@huawei.com> (raw)
Correct the wrong param name @addr to @p.
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
---
include/asm-generic/bitops/lock.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/asm-generic/bitops/lock.h b/include/asm-generic/bitops/lock.h
index 3ae021368f48..cdd4fde2dacc 100644
--- a/include/asm-generic/bitops/lock.h
+++ b/include/asm-generic/bitops/lock.h
@@ -9,7 +9,7 @@
/**
* test_and_set_bit_lock - Set a bit and return its old value, for lock
* @nr: Bit to set
- * @addr: Address to count from
+ * @p: Address to count from
*
* This operation is atomic and provides acquire barrier semantics if
* the returned value is 0.
@@ -33,7 +33,7 @@ static inline int test_and_set_bit_lock(unsigned int nr,
/**
* clear_bit_unlock - Clear a bit in memory, for unlock
* @nr: the bit to set
- * @addr: the address to start counting from
+ * @p: the address to start counting from
*
* This operation is atomic and provides release barrier semantics.
*/
@@ -46,7 +46,7 @@ static inline void clear_bit_unlock(unsigned int nr, volatile unsigned long *p)
/**
* __clear_bit_unlock - Clear a bit in memory, for unlock
* @nr: the bit to set
- * @addr: the address to start counting from
+ * @p: the address to start counting from
*
* A weaker form of clear_bit_unlock() as used by __bit_lock_unlock(). If all
* the bits in the word are protected by this lock some archs can use weaker
@@ -69,7 +69,7 @@ static inline void __clear_bit_unlock(unsigned int nr,
* clear_bit_unlock_is_negative_byte - Clear a bit in memory and test if bottom
* byte is negative, for unlock.
* @nr: the bit to clear
- * @addr: the address to start counting from
+ * @p: the address to start counting from
*
* This is a bit of a one-trick-pony for the filemap code, which clears
* PG_locked and tests PG_waiters,
--
2.19.1
next reply other threads:[~2020-09-10 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 9:10 Miaohe Lin [this message]
2020-09-30 9:57 linmiaohe
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=20200910091004.8921-1-linmiaohe@huawei.com \
--to=linmiaohe@huawei.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®