From: Greg KH <gregkh@linuxfoundation.org>
To: Martin Liu <liumartin@google.com>
Cc: heikki.krogerus@linux.intel.com, johan@kernel.org,
stern@rowland.harvard.edu, andy.shevchenko@gmail.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
jenhaochen@google.com
Subject: Re: [RFC PATCH v3] driver core: hold dev's parent lock when needed
Date: Tue, 29 May 2018 18:59:00 +0200 [thread overview]
Message-ID: <20180529165900.GA15599@kroah.com> (raw)
In-Reply-To: <20180529163428.234106-1-liumartin@google.com>
On Wed, May 30, 2018 at 12:34:29AM +0800, Martin Liu wrote:
> SOC have internal I/O buses that can't be proved for devices. The
> devices on the buses can be accessed directly without additinal
> configuration required. This type of bus is represented as
> "simple-bus". In some platforms, we name "soc" with "simple-bus"
> attribute and many devices are hooked under it desribed in DT
> (device tree).
<snip>
Hint, I don't apply "RFC" patches as obviously the author does not think
it is good enough to be merged :)
next prev parent reply other threads:[~2018-05-29 16:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 14:12 [RFC] driver core: don't hold dev's parent lock when using async probe martin_liu
2018-05-22 17:09 ` Alan Stern
2018-05-24 14:00 ` Martin Liu
2018-05-24 15:02 ` Alan Stern
2018-05-24 16:05 ` Martin Liu
2018-05-29 7:07 ` [RFC PATCH v2] driver core: hold dev's parent lock when needed martin_liu
2018-05-29 7:47 ` Greg KH
2018-05-29 14:07 ` Alan Stern
2018-05-29 16:34 ` [RFC PATCH v3] " Martin Liu
2018-05-29 16:59 ` Greg KH [this message]
2018-05-29 17:08 ` Andy Shevchenko
2018-05-29 18:49 ` Alan Stern
2018-05-30 16:31 ` [PATCH v4] " Martin Liu
2018-05-30 17:21 ` Alan Stern
2018-05-31 6:31 ` Greg KH
2018-05-31 7:27 ` Martin Liu
2018-05-31 18:55 ` Andy Shevchenko
2018-05-29 15:28 ` [RFC PATCH v2] " Andy Shevchenko
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=20180529165900.GA15599@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jenhaochen@google.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=liumartin@google.com \
--cc=stern@rowland.harvard.edu \
/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