From: "Paul E. McKenney" <paulmck@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Joel Fernandes <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
rcu@vger.kernel.org, fweisbec@gmail.com, urezki@gmail.com
Subject: Re: [PATCH v2 rcu/dev 1/2] rcu: Track laziness during boot and suspend
Date: Tue, 17 Jan 2023 19:51:55 -0800 [thread overview]
Message-ID: <20230118035155.GR2948950@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20230117164029.434a2336@gandalf.local.home>
On Tue, Jan 17, 2023 at 04:40:29PM -0500, Steven Rostedt wrote:
> On Tue, 17 Jan 2023 11:37:34 -0800
> "Paul E. McKenney" <paulmck@kernel.org> wrote:
>
> > > The reason for the export should have been mentioned in the change log if
> > > the patch is not obvious to why it is being exported.
> >
> > Would something like this suffice? With attribution, of course.
> >
> > Export rcu_async_should_hurry(), rcu_async_hurry(), and
> > rcu_async_relax() for later use by rcutorture.
>
> Yes thanks. That way, at least a git blame will give some rationale for the
> export.
Very well, I will apply this on my next rebase.
Thanx, Paul
prev parent reply other threads:[~2023-01-18 3:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 0:52 Joel Fernandes (Google)
2023-01-12 0:52 ` [PATCH v2 rcu/dev 2/2] rcu: Disable laziness if lazy-tracking says so Joel Fernandes (Google)
2023-01-15 20:54 ` Steven Rostedt
2023-01-15 21:29 ` Joel Fernandes
2023-01-12 1:29 ` [PATCH v2 rcu/dev 1/2] rcu: Track laziness during boot and suspend Paul E. McKenney
2023-01-12 1:56 ` Joel Fernandes
2023-01-12 19:27 ` Paul E. McKenney
2023-01-12 22:25 ` Joel Fernandes
2023-01-12 23:50 ` Paul E. McKenney
2023-01-15 21:25 ` Steven Rostedt
2023-01-15 21:34 ` Joel Fernandes
2023-01-16 4:26 ` Paul E. McKenney
2023-01-17 19:32 ` Steven Rostedt
2023-01-17 19:37 ` Paul E. McKenney
2023-01-17 19:45 ` Joel Fernandes
2023-01-17 21:40 ` Steven Rostedt
2023-01-18 3:51 ` 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=20230118035155.GR2948950@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.com \
/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®