From: Greg KH <gregkh@linuxfoundation.org>
To: Vivek Gautam <gautam.vivek@samsung.com>
Cc: linux-usb@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
balbi@ti.com, stern@rowland.harvard.edu, kgene.kim@samsung.com,
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 2/2] usb: dwc3-exynos: Fix compatible strings for the device
Date: Thu, 24 Jan 2013 13:32:13 -0800 [thread overview]
Message-ID: <20130124213213.GA21329@kroah.com> (raw)
In-Reply-To: <1359035130-22667-3-git-send-email-gautam.vivek@samsung.com>
On Thu, Jan 24, 2013 at 07:15:30PM +0530, Vivek Gautam wrote:
> Using specific chip in compatible strings. Newer SOCs can claim
> device by using older string in the compatible list.
>
> Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
> Reviewed-by: Doug Anderson <dianders@chromium.org>
> ---
> drivers/usb/dwc3/dwc3-exynos.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Felipe, want me to take this one, or will you?
thanks,
greg k-h
next prev parent reply other threads:[~2013-01-24 21:32 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
2013-01-24 13:45 ` [PATCH v2 1/2] usb: ehci-s5p/ohci-exynos: Fix compatible strings for the device Vivek Gautam
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
2013-01-24 21:32 ` Greg KH [this message]
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
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=20130124213213.GA21329@kroah.com \
--to=gregkh@linuxfoundation.org \
--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=jg1.han@samsung.com \
--cc=kgene.kim@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