From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Vivek Gautam' <gautam.vivek@samsung.com>, linux-usb@vger.kernel.org
Cc: devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
gregkh@linuxfoundation.org, balbi@ti.com,
stern@rowland.harvard.edu, thomas.abraham@linaro.org,
rob.herring@calxeda.com, grant.likely@secretlab.ca,
sylvester.nawrocki@gmail.com, dianders@chromium.org,
jg1.han@samsung.com, cpgs@samsung.com
Subject: RE: [PATCH v2 0/2] usb: exynos: Fix compatible strings used for device
Date: Fri, 25 Jan 2013 10:01:32 -0800 [thread overview]
Message-ID: <010e01cdfb26$04adcb00$0e096100$@samsung.com> (raw)
In-Reply-To: <1359035130-22667-1-git-send-email-gautam.vivek@samsung.com>
Vivek Gautam wrote:
>
> Using chip specific compatible string as it should be.
> So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
> which till now used a generic 'exynos' in their compatible strings.
>
> Changes from v1:
> - Changing compatible string from "samsung,exynos5250-dwc3" to
> "samsung,exynos5250-dwusb3" as per discussion happened in
> thread:
> [PATCH 0/2] usb: exynos: Fix compatible strings used for device.
>
> Vivek Gautam (2):
> usb: ehci-s5p/ohci-exynos: Fix compatible strings for the device
> usb: dwc3-exynos: Fix compatible strings for the device
>
> drivers/usb/dwc3/dwc3-exynos.c | 2 +-
> drivers/usb/host/ehci-s5p.c | 2 +-
> drivers/usb/host/ohci-exynos.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
For now, I'm fine on this series, I'm still thinking we need to sort out the
chip name in compatible for IP though.
Felipe, please go ahead, if you want my ack, feel free to add:
Acked-by: Kukjin Kim <kgene.kim@samsung.com>
Thanks.
- Kukjin
prev parent reply other threads:[~2013-01-25 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 13:45 [PATCH v2 0/2] usb: exynos: Fix compatible strings used for device Vivek Gautam
[not found] ` <1359035130-22667-1-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-01-24 13:45 ` [PATCH v2 1/2] usb: ehci-s5p/ohci-exynos: Fix compatible strings for the device Vivek Gautam
[not found] ` <1359035130-22667-2-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-01-24 16:27 ` Alan Stern
2013-01-25 2:01 ` Jingoo Han
2013-01-24 13:45 ` [PATCH v2 2/2] usb: dwc3-exynos: " Vivek Gautam
[not found] ` <1359035130-22667-3-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-01-24 21:32 ` Greg KH
2013-01-24 22:32 ` Felipe Balbi
2013-01-24 14:01 ` [PATCH v2 0/2] usb: exynos: Fix compatible strings used for device Vivek Gautam
2013-01-25 18:01 ` 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='010e01cdfb26$04adcb00$0e096100$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=balbi@ti.com \
--cc=cpgs@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dianders@chromium.org \
--cc=gautam.vivek@samsung.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--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=rob.herring@calxeda.com \
--cc=stern@rowland.harvard.edu \
--cc=sylvester.nawrocki@gmail.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;
as well as URLs for NNTP newsgroup(s).