From: chunfeng.yun@mediatek.com (Chunfeng Yun)
To: linux-arm-kernel@lists.infradead.org
Subject: [usb-next, v3 PATCH] usb: xhci: skip phys initialization of shared hcd
Date: Fri, 23 Mar 2018 11:20:48 +0800 [thread overview]
Message-ID: <1521775248.3717.159.camel@mhfsdcap03> (raw)
In-Reply-To: <20180322125300.GA22130@kroah.com>
On Thu, 2018-03-22 at 13:53 +0100, Greg Kroah-Hartman wrote:
> On Thu, Mar 22, 2018 at 08:12:50PM +0800, Chunfeng Yun wrote:
> > The phys has already been initialized when add primary hcd,
> > including usb2 phys and usb3 phys also if exist, so needn't
> > re-parse "phys" property again.
>
> Wait, why does the subject say "xhci", when this is in USB core code?
>
> I'll go edit that by hand...
Thanks
prev parent reply other threads:[~2018-03-23 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 8:39 [usb-next, v2 PATCH] usb: xhci: skip phys initialization of shared hcd Chunfeng Yun
2018-03-22 9:01 ` Greg Kroah-Hartman
2018-03-22 9:21 ` Chunfeng Yun
2018-03-22 12:00 ` Greg Kroah-Hartman
2018-03-22 12:29 ` [usb-next, v3 " Roger Quadros
2018-03-22 12:53 ` Greg Kroah-Hartman
2018-03-23 3:20 ` Chunfeng Yun [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=1521775248.3717.159.camel@mhfsdcap03 \
--to=chunfeng.yun@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).