All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH rcu] rcutorture: __pcpu_scope_rcu_torture_timer_rand can be static
Date: Tue, 22 May 2018 16:21:16 -0700	[thread overview]
Message-ID: <20180522232116.GG3803@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180522213034.GA87654@lkp-sb04>

On Wed, May 23, 2018 at 05:30:35AM +0800, kbuild test robot wrote:
> 
> Fixes: 816e0790625a ("rcutorture: Use per-CPU random state for rcu_torture_timer()")
> Signed-off-by: kbuild test robot <fengguang.wu@intel.com>

I folded this into the offending patch with attribution, thank you!

							Thanx, Paul

> ---
>  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;
>  }
> 
> -DEFINE_TORTURE_RANDOM_PERCPU(rcu_torture_timer_rand);
> +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 23:30 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 ` [RFC PATCH rcu] rcutorture: __pcpu_scope_rcu_torture_timer_rand can be static kbuild test robot
2018-05-22 23:21   ` 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=20180522232116.GG3803@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.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.