From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.19.y-cip 0/4] Add USB support
Date: Wed, 11 Sep 2019 09:54:27 +0200 [thread overview]
Message-ID: <20190911075427.GA9517@amd> (raw)
In-Reply-To: <1568019126-45985-1-git-send-email-biju.das@bp.renesas.com>
Hi!
> This patch series add USB2.0/USB3.0 support for Hihope RZ/G2M platform.
>
> This patch series is based on linux-4.19.y-cip and all the patches
> in this series are cherry-picked from linux rc tree.
>
> Biju Das (3):
> arm64: dts: renesas: r8a774a1: Fix USB 2.0 clocks
> arm64: dts: renesas: hihope-common: Add USB 2.0 support
> arm64: dts: renesas: hihope-common: Enable USB3.0
>
> Yoshihiro Shimoda (1):
> phy: renesas: rcar-gen3-usb2: fix imbalance powered flag
Nothing obviously wrong here. Let me apply the series...
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190911/be18f014/attachment.sig>
next prev parent reply other threads:[~2019-09-11 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 8:52 [cip-dev] [PATCH 4.19.y-cip 0/4] Add USB support Biju Das
2019-09-09 8:52 ` [cip-dev] [PATCH 4.19.y-cip 1/4] phy: renesas: rcar-gen3-usb2: fix imbalance powered flag Biju Das
2019-09-09 8:52 ` [cip-dev] [PATCH 4.19.y-cip 2/4] arm64: dts: renesas: r8a774a1: Fix USB 2.0 clocks Biju Das
2019-09-09 8:52 ` [cip-dev] [PATCH 4.19.y-cip 3/4] arm64: dts: renesas: hihope-common: Add USB 2.0 support Biju Das
2019-09-09 8:52 ` [cip-dev] [PATCH 4.19.y-cip 4/4] arm64: dts: renesas: hihope-common: Enable USB3.0 Biju Das
2019-09-11 7:54 ` Pavel Machek [this message]
2019-09-11 13:39 ` [cip-dev] [PATCH 4.19.y-cip 0/4] Add USB support Pavel Machek
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=20190911075427.GA9517@amd \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.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).