From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yinbo Zhu <yinbo.zhu@nxp.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Xiaobo Xie <xiaobo.xie@nxp.com>,
Jerry Huang <jerry.huang@nxp.com>, Ran Wang <ran.wang_1@nxp.com>,
Ramneek Mehresh <ramneek.mehresh@freescale.com>,
Nikhil Badola <nikhil.badola@freescale.com>,
Suresh Gupta <suresh.gupta@freescale.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/6] usb: fsl: Set USB_EN bit to select ULPI phy
Date: Tue, 22 Jan 2019 09:08:13 +0100 [thread overview]
Message-ID: <20190122080813.GA21793@kroah.com> (raw)
In-Reply-To: <20190121102601.4735-1-yinbo.zhu@nxp.com>
On Mon, Jan 21, 2019 at 10:25:00AM +0000, Yinbo Zhu wrote:
> From: Nikhil Badola <nikhil.badola@freescale.com>
>
> Set USB_EN bit to select ULPI phy for USB controller version 2.5
>
> Signed-off-by: Nikhil Badola <nikhil.badola@freescale.com>
> Signed-off-by: Yinbo Zhu <yinbo.zhu@nxp.com>
> ---
> Change in v2:
> replace Yinbo.Zhu with Yinbo Zhu
>
> drivers/usb/host/ehci-fsl.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
This patch doesn't apply against my usb-next branch, what did you
generate it against?
thanks,
greg k-h
prev parent reply other threads:[~2019-01-22 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 10:25 [PATCH v2 1/6] usb: fsl: Set USB_EN bit to select ULPI phy Yinbo Zhu
2019-01-21 10:25 ` [PATCH v2 2/6] usb: phy: Workaround for USB erratum-A005728 Yinbo Zhu
2019-01-21 10:25 ` [PATCH v2 3/6] usb: host: Stops USB controller init if PLL fails to lock Yinbo Zhu
2019-01-22 8:04 ` Greg Kroah-Hartman
2019-01-21 10:25 ` [PATCH v2 4/6] usb: linux/fsl_device: Add platform member has_fsl_erratum_a006918 Yinbo Zhu
2019-01-21 10:25 ` [PATCH v2 5/6] usb: linux/fsl_device: Add platform member has_fsl_erratum_14 Yinbo Zhu
2019-01-21 10:25 ` [PATCH v2 6/6] usb :fsl: Change string format for errata property Yinbo Zhu
2019-01-22 8:08 ` 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=20190122080813.GA21793@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jerry.huang@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nikhil.badola@freescale.com \
--cc=ramneek.mehresh@freescale.com \
--cc=ran.wang_1@nxp.com \
--cc=stern@rowland.harvard.edu \
--cc=suresh.gupta@freescale.com \
--cc=xiaobo.xie@nxp.com \
--cc=yinbo.zhu@nxp.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