From: Kishon Vijay Abraham I <kishon@ti.com>
To: <gregkh@linuxfoundation.org>
Cc: <kishon@ti.com>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] PHY: for 4.18 -rc
Date: Wed, 11 Jul 2018 14:47:50 +0530 [thread overview]
Message-ID: <20180711091750.2365-1-kishon@ti.com> (raw)
Hi Greg,
I have a couple of patches to be included in this -rc cycle. One gets xhci
working after disable->enable cycle in broadcom SoC and the other fixes
a compilation warning in Motorola USB PHY.
Consider merging it in this -rc cycle.
Thanks
Kishon
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git tags/phy-for-4.18-rc
for you to fetch changes up to ad5003300b077bf1af15e667097b3b1f73288177:
phy: mapphone-mdm6600: Fix wrong enum used for status lines (2018-06-29 12:00:22 +0530)
----------------------------------------------------------------
phy: for 4.18-rc
*) Fix to get xhci working after disable<->enable cycle
*) Fix wrong enum used for status lines (also fixes a compilation
warning).
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
----------------------------------------------------------------
Jaedon Shin (1):
phy: phy-brcm-usb-init: Fix power down USB 3.0 PHY when XHCI reenabled
Tony Lindgren (1):
phy: mapphone-mdm6600: Fix wrong enum used for status lines
drivers/phy/broadcom/phy-brcm-usb-init.c | 4 ++++
drivers/phy/motorola/phy-mapphone-mdm6600.c | 4 ++--
2 files changed, 6 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2018-07-11 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 9:17 Kishon Vijay Abraham I [this message]
2018-07-16 11:29 ` Greg KH
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=20180711091750.2365-1-kishon@ti.com \
--to=kishon@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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
Powered by JetHome