From: "Paul E. McKenney" <paulmck@kernel.org>
To: Wang Qing <wangqing@vivo.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Josh Triplett <josh@joshtriplett.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] locking: remove duplicate include of percpu-rwsem.h
Date: Sat, 7 Nov 2020 11:30:26 -0800 [thread overview]
Message-ID: <20201107193026.GE3249@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <1604737443-16241-1-git-send-email-wangqing@vivo.com>
On Sat, Nov 07, 2020 at 04:24:03PM +0800, Wang Qing wrote:
> Remove duplicate header include which is unnecessary.
>
> Signed-off-by: Wang Qing <wangqing@vivo.com>
Queued for further review and testing, thank you!
I had to apply against v5.10-rc1 and then cherry-pick the result, which
did work fine. However, in the future, could you please post patches
against the -rcu tree's "dev" branch?
Please see https://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
for more information.
And as always, I could not resist a bit of wordsmithing, so please see
below and let me know if I messed anything up.
Thanx, Paul
------------------------------------------------------------------------
commit ad6dcb7c338ad322ddeeb75594bc77dcdbeb43de
Author: Wang Qing <wangqing@vivo.com>
Date: Sat Nov 7 16:24:03 2020 +0800
locking: Remove duplicate include of percpu-rwsem.h
This commit removes an unnecessary #include.
Signed-off-by: Wang Qing <wangqing@vivo.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
diff --git a/kernel/locking/locktorture.c b/kernel/locking/locktorture.c
index fd838ce..0ab94e1 100644
--- a/kernel/locking/locktorture.c
+++ b/kernel/locking/locktorture.c
@@ -27,7 +27,6 @@
#include <linux/moduleparam.h>
#include <linux/delay.h>
#include <linux/slab.h>
-#include <linux/percpu-rwsem.h>
#include <linux/torture.h>
#include <linux/reboot.h>
prev parent reply other threads:[~2020-11-07 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 8:24 Wang Qing
2020-11-07 19:30 ` Paul E. McKenney [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=20201107193026.GE3249@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=dave@stgolabs.net \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangqing@vivo.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®