From: zuoqilin1@163.com
To: peterz@infradead.org, mingo@redhat.com, longman@redhat.com,
boqun.feng@gmail.com, will@kernel.org
Cc: linux-kernel@vger.kernel.org, zuoqilin <zuoqilin@yulong.com>
Subject: [PATCH] include/linux: remove duplicate description
Date: Tue, 23 Feb 2021 17:25:39 +0800 [thread overview]
Message-ID: <20210223092539.941-1-zuoqilin1@163.com> (raw)
From: zuoqilin <zuoqilin@yulong.com>
linux/spinlock.h
Signed-off-by: zuoqilin <zuoqilin@yulong.com>
---
include/linux/spinlock.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/spinlock.h b/include/linux/spinlock.h
index 7989784..732150e 100644
--- a/include/linux/spinlock.h
+++ b/include/linux/spinlock.h
@@ -43,8 +43,6 @@
*
* linux/spinlock_api_up.h:
* builds the _spin_*() APIs.
- *
- * linux/spinlock.h: builds the final spin_*() APIs.
*/
#include <linux/typecheck.h>
--
1.9.1
next reply other threads:[~2021-02-23 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 9:25 zuoqilin1 [this message]
2021-02-23 11:32 ` [PATCH] include/linux: remove duplicate description Peter Zijlstra
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=20210223092539.941-1-zuoqilin1@163.com \
--to=zuoqilin1@163.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=zuoqilin@yulong.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;
as well as URLs for NNTP newsgroup(s).