From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Vivek Gautam'" <gautam.vivek@samsung.com>,
linux-usb@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, balbi@ti.com,
rob.herring@calxeda.com, thomas.abraham@linaro.org,
grant.likely@secretlab.ca, dianders@chromium.org,
jg1.han@samsung.com, p.paneri@samsung.com
Subject: RE: [PATCH v4 0/2] ARM: Exynos5250: Enabling samsung usb phy
Date: Wed, 10 Apr 2013 19:31:29 +0900 [thread overview]
Message-ID: <310001ce35d6$901546b0$b03fd410$%kim@samsung.com> (raw)
In-Reply-To: <1363334171-21812-1-git-send-email-gautam.vivek@samsung.com>
Vivek Gautam wrote:
>
> Based on 'for-next' of linux-samsung tree with following patches
> from Doug on top:
> usb: Document clocks in samsung, exynos4210-ehci/ohci bindings
> ARM: dts: add usb 2.0 clock references to exynos5250 device tree
>
> Also depending upon following patch-series for Samsung-usb-phy driver:
> [PATCH v7 0/2] Adding USB 3.0 DRD-phy support for exynos5250
>
> Changes from v3:
> Added 'clocks' and 'clock-names' entry also in device nodes, aligning
> with common clock framework for Samsung's SoCs.
>
> Vivek Gautam (2):
> ARM: Exynos5250: Enabling samsung-usb2phy driver
> ARM: Exynos5250: Enabling samsung-usb3phy driver
>
> arch/arm/boot/dts/exynos5250.dtsi | 29 +++++++++++++++++++++++++++++
> 1 files changed, 29 insertions(+), 0 deletions(-)
>
> --
> 1.7.6.5
OK, applied, thanks.
- Kukjin
prev parent reply other threads:[~2013-04-10 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 7:56 Vivek Gautam
2013-03-15 7:56 ` [PATCH v4 1/2] ARM: Exynos5250: Enabling samsung-usb2phy driver Vivek Gautam
2013-03-15 7:56 ` [PATCH v4 2/2] ARM: Exynos5250: Enabling samsung-usb3phy driver Vivek Gautam
2013-04-04 6:46 ` [PATCH v4 0/2] ARM: Exynos5250: Enabling samsung usb phy Vivek Gautam
2013-04-10 10:31 ` Kukjin Kim [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='310001ce35d6$901546b0$b03fd410$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dianders@chromium.org \
--cc=gautam.vivek@samsung.com \
--cc=grant.likely@secretlab.ca \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.paneri@samsung.com \
--cc=rob.herring@calxeda.com \
--cc=thomas.abraham@linaro.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
all inboxes | Powered by JetHome®