From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v4 1/4] devres: Make locking straight forward in release_nodes()
Date: Tue, 15 Jun 2021 17:14:26 +0200 [thread overview]
Message-ID: <YMjD0kUXZasI+vyY@kroah.com> (raw)
In-Reply-To: <YMM3HYt2q5i35OUv@smile.fi.intel.com>
On Fri, Jun 11, 2021 at 01:12:45PM +0300, Andy Shevchenko wrote:
> On Wed, May 26, 2021 at 02:53:57PM +0300, Andy Shevchenko wrote:
> > On Mon, May 17, 2021 at 03:29:43PM +0300, Andy Shevchenko wrote:
> > > It seems for the sake of saving stack memory of couple of pointers,
> > > the locking in release_nodes() callers becomes interesting.
> > >
> > > Replace this logic with a straight forward locking and unlocking scheme.
> >
> > Any comments on the series?
>
> Greg, Rafael, anything I should do here?
Sorry for the delay. This looks good to me, and it's a step forward
into adding tracing to the driver core, which I've wanted to add for a
while now.
So I'll take it, thanks!
greg k-h
prev parent reply other threads:[~2021-06-15 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 12:29 [PATCH v4 1/4] devres: Make locking straight forward in release_nodes() Andy Shevchenko
2021-05-17 12:29 ` [PATCH v4 2/4] devres: Use list_for_each_safe_from() in remove_nodes() Andy Shevchenko
2021-05-17 12:29 ` [PATCH v4 3/4] devres: No need to call remove_nodes() when there none present Andy Shevchenko
2021-05-17 12:29 ` [PATCH v4 4/4] devres: Enable trace events Andy Shevchenko
2021-05-26 11:53 ` [PATCH v4 1/4] devres: Make locking straight forward in release_nodes() Andy Shevchenko
2021-06-11 10:12 ` Andy Shevchenko
2021-06-15 15:14 ` Greg Kroah-Hartman [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=YMjD0kUXZasI+vyY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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