RCU Archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Zqiang <qiang.zhang1211@gmail.com>
Cc: frederic@kernel.org, neeraj.upadhyay@kernel.org,
	joel@joelfernandes.org, rcu@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Generate get_gp_data method to print gp status of different types of rcutorture tests
Date: Mon, 18 Mar 2024 21:58:53 -0700	[thread overview]
Message-ID: <0071dd1c-310f-43c3-bb0b-694d0cbe0ed8@paulmck-laptop> (raw)
In-Reply-To: <20240318093412.17258-1-qiang.zhang1211@gmail.com>

On Mon, Mar 18, 2024 at 05:34:10PM +0800, Zqiang wrote:
> This commit is mainly to enable rcutorture testing to support print
> rcu-tasks related gp state, and remove redundant function pointer
> initialization in rcu_torture_ops structure's objects.
> 
> Zqiang (2):
>   rcutorture: Make rcutorture support print rcu-tasks gp state
>   rcutorture: Removing redundant function pointer initialization

Queued for v6.10, thank you!

							Thanx, Paul

>  kernel/rcu/rcu.h        | 20 ++++++++++----------
>  kernel/rcu/rcutorture.c | 38 ++++++++++++++++++--------------------
>  kernel/rcu/srcutree.c   |  5 +----
>  kernel/rcu/tasks.h      | 21 +++++++++++++++++++++
>  kernel/rcu/tree.c       | 13 +++----------
>  5 files changed, 53 insertions(+), 44 deletions(-)
> 
> -- 
> 2.17.1
> 

      parent reply	other threads:[~2024-03-19  4:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18  9:34 [PATCH v3 0/2] Generate get_gp_data method to print gp status of different types of rcutorture tests Zqiang
2024-03-18  9:34 ` [PATCH v3 1/2] rcutorture: Make rcutorture support print rcu-tasks gp state Zqiang
2024-03-18  9:34 ` [PATCH v3 2/2] rcutorture: Removing redundant function pointer initialization Zqiang
2024-03-19  4:58 ` 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=0071dd1c-310f-43c3-bb0b-694d0cbe0ed8@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neeraj.upadhyay@kernel.org \
    --cc=qiang.zhang1211@gmail.com \
    --cc=rcu@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).