From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Ethan Hansen <1ethanhansen@gmail.com>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
joel@joelfernandes.org
Subject: Re: [PATCH tip/core/rcu 1/1] rcu: Remove unused function rcutorture_record_progress
Date: Thu, 1 Aug 2019 16:22:24 -0700 [thread overview]
Message-ID: <20190801232224.GT5913@linux.ibm.com> (raw)
In-Reply-To: <1564693240-13363-1-git-send-email-1ethanhansen@gmail.com>
On Thu, Aug 01, 2019 at 02:00:40PM -0700, Ethan Hansen wrote:
> The function rcutorture_record_progress is declared in rcu.h,
> but is never used. Remove rcutorture_record_progress to clean code.
>
> Signed-off-by: Ethan Hansen <1ethanhansen@gmail.com>
Good eyes! Queued, likely for v5.5, thank you!
Thanx, Paul
> ---
> kernel/rcu/rcu.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/kernel/rcu/rcu.h b/kernel/rcu/rcu.h
> index 8fd4f82..aeec70f 100644
> --- a/kernel/rcu/rcu.h
> +++ b/kernel/rcu/rcu.h
> @@ -455,7 +455,6 @@ enum rcutorture_type {
> #if defined(CONFIG_TREE_RCU) || defined(CONFIG_PREEMPT_RCU)
> void rcutorture_get_gp_data(enum rcutorture_type test_type, int *flags,
> unsigned long *gp_seq);
> -void rcutorture_record_progress(unsigned long vernum);
> void do_trace_rcu_torture_read(const char *rcutorturename,
> struct rcu_head *rhp,
> unsigned long secs,
> @@ -468,7 +467,6 @@ static inline void rcutorture_get_gp_data(enum rcutorture_type test_type,
> *flags = 0;
> *gp_seq = 0;
> }
> -static inline void rcutorture_record_progress(unsigned long vernum) { }
> #ifdef CONFIG_RCU_TRACE
> void do_trace_rcu_torture_read(const char *rcutorturename,
> struct rcu_head *rhp,
> --
> 1.8.3.1
>
prev parent reply other threads:[~2019-08-01 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 21:00 [PATCH tip/core/rcu 1/1] rcu: Remove unused function rcutorture_record_progress Ethan Hansen
2019-08-01 23:22 ` 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=20190801232224.GT5913@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=1ethanhansen@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.