From: Peter Zijlstra <peterz@infradead.org>
To: zuoqilin1@163.com
Cc: mingo@redhat.com, longman@redhat.com, boqun.feng@gmail.com,
will@kernel.org, linux-kernel@vger.kernel.org,
zuoqilin <zuoqilin@yulong.com>
Subject: Re: [PATCH] include/linux: remove duplicate description
Date: Tue, 23 Feb 2021 12:32:07 +0100 [thread overview]
Message-ID: <YDTnt8SDTLJlPlP1@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210223092539.941-1-zuoqilin1@163.com>
On Tue, Feb 23, 2021 at 05:25:39PM +0800, zuoqilin1@163.com wrote:
> 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.
> */
I think not, now the UP comment it incomplete.
prev parent reply other threads:[~2021-02-23 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 9:25 [PATCH] include/linux: remove duplicate description zuoqilin1
2021-02-23 11:32 ` Peter Zijlstra [this message]
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=YDTnt8SDTLJlPlP1@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=will@kernel.org \
--cc=zuoqilin1@163.com \
--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).