public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Liu Song <fishland@aliyun.com>
Cc: josh@joshtriplett.org, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
	linux-kernel@vger.kernel.org, liu.song11@zte.com.cn
Subject: Re: [PATCH] rcu: Print correct in print_one_rcu_pending
Date: Mon, 10 Dec 2018 10:03:19 -0800	[thread overview]
Message-ID: <20181210180319.GU4170@linux.ibm.com> (raw)
In-Reply-To: <20181210153557.3110-1-fishland@aliyun.com>

On Mon, Dec 10, 2018 at 11:35:56PM +0800, Liu Song wrote:
> My kernel version is 4.4.166 and I found incorrect print info
> from print_one_rcu_pending. Adjust the description to make the
> information correct.
> 
> Signed-off-by: Liu Song <liu.song11@zte.com.cn>

This does not apply to mainline because debugfs tracing has been removed.

Please do feel free to send it to -stable, though I have no idea what the
-stable folks do about fixes to things that are no longer in mainline.
In that case, it is clear that the rule about waiting until it gets to
mainline isn't appropriate.  ;-)

							Thanx, Paul

> ---
>  kernel/rcu/tree_trace.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/rcu/tree_trace.c b/kernel/rcu/tree_trace.c
> index ef7093cc9b5c..5d0eddc9dc63 100644
> --- a/kernel/rcu/tree_trace.c
> +++ b/kernel/rcu/tree_trace.c
> @@ -365,7 +365,7 @@ static void print_one_rcu_pending(struct seq_file *m, struct rcu_data *rdp)
>  		   rdp->n_rp_report_qs,
>  		   rdp->n_rp_cb_ready,
>  		   rdp->n_rp_cpu_needs_gp);
> -	seq_printf(m, "gpc=%ld gps=%ld nn=%ld ndw%ld\n",
> +	seq_printf(m, "gpc=%ld gps=%ld ndw=%ld nn=%ld\n",
>  		   rdp->n_rp_gp_completed,
>  		   rdp->n_rp_gp_started,
>  		   rdp->n_rp_nocb_defer_wakeup,
> -- 
> 2.19.1
> 


           reply	other threads:[~2018-12-10 18:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20181210153557.3110-1-fishland@aliyun.com>]

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=20181210180319.GU4170@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=fishland@aliyun.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liu.song11@zte.com.cn \
    --cc=mathieu.desnoyers@efficios.com \
    --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