From: Heiko Stuebner <heiko@sntech.de>
To: linux-usb@vger.kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
balbi@kernel.org, gregkh@linuxfoundation.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
cl@rock-chips.com, hminas@synopsys.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] add dwc2 support for px30
Date: Mon, 24 Sep 2018 15:47:12 +0200 [thread overview]
Message-ID: <102522978.rGKrA9VWk8@phil> (raw)
In-Reply-To: <20180802130133.4898-1-heiko@sntech.de>
Am Donnerstag, 2. August 2018, 15:01:30 CEST schrieb Heiko Stuebner:
> This is split out from the series adding the px30 support, due to
> the dwc2 binding change not having landed yet in a maintainer tree.
>
> The Acked binding change should go through some usb tree, while
> I'll pick up the dts changes once that has happened.
>
> The binding itself is unchanged.
>
>
> Heiko Stuebner (2):
> arm64: dts: rockchip: add dwc2 otg controller on px30
> arm64: dts: rockchip: enable dwc2-based otg controller on px30-evb
>
> Liang Chen (1):
> dt-bindings: usb: dwc2: add description for px30
applied all 3 patches for 4.20 now.
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] add dwc2 support for px30
Date: Mon, 24 Sep 2018 15:47:12 +0200 [thread overview]
Message-ID: <102522978.rGKrA9VWk8@phil> (raw)
In-Reply-To: <20180802130133.4898-1-heiko@sntech.de>
Am Donnerstag, 2. August 2018, 15:01:30 CEST schrieb Heiko Stuebner:
> This is split out from the series adding the px30 support, due to
> the dwc2 binding change not having landed yet in a maintainer tree.
>
> The Acked binding change should go through some usb tree, while
> I'll pick up the dts changes once that has happened.
>
> The binding itself is unchanged.
>
>
> Heiko Stuebner (2):
> arm64: dts: rockchip: add dwc2 otg controller on px30
> arm64: dts: rockchip: enable dwc2-based otg controller on px30-evb
>
> Liang Chen (1):
> dt-bindings: usb: dwc2: add description for px30
applied all 3 patches for 4.20 now.
next prev parent reply other threads:[~2018-09-24 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 13:01 [PATCH 0/3] add dwc2 support for px30 Heiko Stuebner
2018-08-02 13:01 ` Heiko Stuebner
2018-08-02 13:01 ` [PATCH 1/3] dt-bindings: usb: dwc2: add description " Heiko Stuebner
2018-08-02 13:01 ` Heiko Stuebner
2018-08-02 13:01 ` [1/3] " Heiko Stuebner
2018-09-10 12:36 ` [PATCH 1/3] " Heiko Stuebner
2018-09-10 12:36 ` Heiko Stuebner
2018-09-10 12:36 ` [1/3] " Heiko Stuebner
2018-08-02 13:01 ` [PATCH 2/3] arm64: dts: rockchip: add dwc2 otg controller on px30 Heiko Stuebner
2018-08-02 13:01 ` Heiko Stuebner
2018-08-02 13:01 ` [2/3] " Heiko Stuebner
2018-08-02 13:01 ` [PATCH 3/3] arm64: dts: rockchip: enable dwc2-based otg controller on px30-evb Heiko Stuebner
2018-08-02 13:01 ` Heiko Stuebner
2018-08-02 13:01 ` [3/3] " Heiko Stuebner
2018-09-24 13:47 ` Heiko Stuebner [this message]
2018-09-24 13:47 ` [PATCH 0/3] add dwc2 support for px30 Heiko Stuebner
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=102522978.rGKrA9VWk8@phil \
--to=heiko@sntech.de \
--cc=balbi@kernel.org \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.