mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel Fernandes <joelagnelf@nvidia.com>
To: paulmck@kernel.org, rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com, rostedt@goodmis.org
Subject: Re: [PATCH 0/5] Miscellaneous rcutorture updates
Date: Fri, 9 May 2025 09:16:41 -0400	[thread overview]
Message-ID: <7b704746-fd7b-4c09-9f5c-cf11ba200379@nvidia.com> (raw)
In-Reply-To: <a942066a-85cb-4932-b4de-0ee39287ab7d@paulmck-laptop>



On 5/8/2025 7:44 PM, Paul E. McKenney wrote:
> Hello!
> 
> This series provides miscellaneous rcutorture updates:
> 
> 1.	Suppress torture.sh "Zero time" messages for disabled tests.
> 
> 2.	Print number of RCU up/down readers and migrations.
> 
> 3.	Check for no up/down readers at task level.
> 
> 4.	Start rcu_torture_writer() after rcu_torture_reader().
> 
> 5.	Print only one rtort_pipe_count splat.

Paul,
Are these for 6.16? I am guessing not so I'll put them in my rcu/dev branch but
let me know.

Thanks.

      parent reply	other threads:[~2025-05-09 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 23:44 Paul E. McKenney
2025-05-08 23:44 ` [PATCH 1/5] torture: Suppress torture.sh "Zero time" messages for disabled tests Paul E. McKenney
2025-05-08 23:44 ` [PATCH 2/5] rcutorture: Print number of RCU up/down readers and migrations Paul E. McKenney
2025-05-08 23:45 ` [PATCH 3/5] rcutorture: Check for no up/down readers at task level Paul E. McKenney
2025-05-08 23:45 ` [PATCH 4/5] rcutorture: Start rcu_torture_writer() after rcu_torture_reader() Paul E. McKenney
2025-05-08 23:45 ` [PATCH 5/5] rcutorture: Print only one rtort_pipe_count splat Paul E. McKenney
2025-05-09 13:16 ` Joel Fernandes [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=7b704746-fd7b-4c09-9f5c-cf11ba200379@nvidia.com \
    --to=joelagnelf@nvidia.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®