From: Li Zhijian <zhijianx.li@intel.com>
To: dave@stgolabs.net, joel@joelfernandes.org, josh@joshtriplett.org,
mathieu.desnoyers@efficios.com, paulmck@kernel.org,
rostedt@goodmis.org, rcu@vger.kernel.org
Cc: philip.li@intel.com, lizhijian@cn.fujitsu.com,
jiangshanlai@gmail.com, linux-kernel@vger.kernel.org,
Li Zhijian <zhijianx.li@intel.com>
Subject: [PATCH 3/6] scftorture: remove unused SCFTORTOUT
Date: Fri, 29 Oct 2021 17:40:26 +0800 [thread overview]
Message-ID: <20211029094029.22501-4-zhijianx.li@intel.com> (raw)
In-Reply-To: <20211029094029.22501-1-zhijianx.li@intel.com>
no one refers to it any more.
Signed-off-by: Li Zhijian <zhijianx.li@intel.com>
---
kernel/scftorture.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/scftorture.c b/kernel/scftorture.c
index f60a7a240f91..5fb15492999b 100644
--- a/kernel/scftorture.c
+++ b/kernel/scftorture.c
@@ -38,9 +38,6 @@
#define SCFTORT_STRING "scftorture"
#define SCFTORT_FLAG SCFTORT_STRING ": "
-#define SCFTORTOUT(s, x...) \
- pr_alert(SCFTORT_FLAG s, ## x)
-
#define VERBOSE_SCFTORTOUT(s, x...) \
do { if (verbose) pr_alert(SCFTORT_FLAG s "\n", ## x); } while (0)
--
2.32.0
next prev parent reply other threads:[~2021-10-29 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 9:40 [PATCH 0/6] minor fixes and cleanups in rcuscale and torture tests Li Zhijian
2021-10-29 9:40 ` [PATCH 1/6] refscale: add missing '\n' to flush message out Li Zhijian
2021-10-29 9:40 ` [PATCH 2/6] scftorture: " Li Zhijian
2021-10-29 9:40 ` Li Zhijian [this message]
2021-10-29 9:40 ` [PATCH 4/6] scftorture: always log error message Li Zhijian
2021-11-02 16:06 ` Paul E. McKenney
2021-11-03 8:24 ` Li Zhijian
2021-10-29 9:40 ` [PATCH 5/6] rcuscale: alwaly " Li Zhijian
2021-10-29 16:40 ` Davidlohr Bueso
2021-11-02 16:09 ` Paul E. McKenney
2021-10-29 9:40 ` [PATCH 6/6] locktorture,rcutorture,torture: always " Li Zhijian
2021-10-29 16:41 ` [PATCH 0/6] minor fixes and cleanups in rcuscale and torture tests Davidlohr Bueso
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=20211029094029.22501-4-zhijianx.li@intel.com \
--to=zhijianx.li@intel.com \
--cc=dave@stgolabs.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhijian@cn.fujitsu.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=philip.li@intel.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).