[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230117164029.434a2336@gandalf.local.home>
Date: Tue, 17 Jan 2023 16:40:29 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: Joel Fernandes <joel@...lfernandes.org>,
linux-kernel@...r.kernel.org,
Josh Triplett <josh@...htriplett.org>,
Lai Jiangshan <jiangshanlai@...il.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
rcu@...r.kernel.org, fweisbec@...il.com, urezki@...il.com
Subject: Re: [PATCH v2 rcu/dev 1/2] rcu: Track laziness during boot and
suspend
On Tue, 17 Jan 2023 11:37:34 -0800
"Paul E. McKenney" <paulmck@...nel.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.
-- Steve
Powered by blists - more mailing lists