LKML Archive on
help / color / mirror / Atom feed
From: kbuild test robot <>
To: "Paul E. McKenney" <>
Subject: [RFC PATCH rcu] rcutorture: __pcpu_scope_rcu_torture_timer_rand can be static
Date: Wed, 23 May 2018 05:30:35 +0800	[thread overview]
Message-ID: <20180522213034.GA87654@lkp-sb04> (raw)
In-Reply-To: <>

Fixes: 816e0790625a ("rcutorture: Use per-CPU random state for rcu_torture_timer()")
Signed-off-by: kbuild test robot <>
 rcutorture.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
index 5683bfb..a03313e 100644
--- a/kernel/rcu/rcutorture.c
+++ b/kernel/rcu/rcutorture.c
@@ -1142,7 +1142,7 @@ static bool rcu_torture_one_read(struct torture_random_state *trsp)
 	return true;
+static DEFINE_TORTURE_RANDOM_PERCPU(rcu_torture_timer_rand);
  * RCU torture reader from timer handler.  Dereferences rcu_torture_current,

  reply	other threads:[~2018-05-22 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 21:30 [rcu:rcu/dev 98/99] kernel/rcu/rcutorture.c:1145:1: sparse: symbol '__pcpu_scope_rcu_torture_timer_rand' was not declared. Should it be static? kbuild test robot
2018-05-22 21:30 ` kbuild test robot [this message]
2018-05-22 23:21   ` [RFC PATCH rcu] rcutorture: __pcpu_scope_rcu_torture_timer_rand can be static Paul E. McKenney

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180522213034.GA87654@lkp-sb04 \ \ \ \ \
    --subject='Re: [RFC PATCH rcu] rcutorture: __pcpu_scope_rcu_torture_timer_rand can be static' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).