devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@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, kgene.kim@samsung.com,
	thomas.abraham@linaro.org, rob.herring@calxeda.com,
	grant.likely@secretlab.ca, sylvester.nawrocki@gmail.com,
	dianders@chromium.org, cpgs@samsung.com,
	'Jingoo Han' <jg1.han@samsung.com>
Subject: Re: [PATCH v2 1/2] usb: ehci-s5p/ohci-exynos: Fix compatible strings for the device
Date: Fri, 25 Jan 2013 11:01:32 +0900	[thread overview]
Message-ID: <00c501cdfa9f$e61a9be0$b24fd3a0$%han@samsung.com> (raw)
In-Reply-To: <1359035130-22667-2-git-send-email-gautam.vivek@samsung.com>

On Thursday, January 24, 2013 10:45 PM, 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>

Acked-by: Jingoo Han <jg1.han@samsung.com>

Best regards,
Jingoo Han

> ---
>  drivers/usb/host/ehci-s5p.c    |    2 +-
>  drivers/usb/host/ohci-exynos.c |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 

  parent reply	other threads:[~2013-01-25  2:01 UTC|newest]

Thread overview: 10+ 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2013-01-25  2:04 [PATCH v2 1/2] usb: ehci-s5p/ohci-exynos: Fix compatible strings for the device Jingoo Han

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='00c501cdfa9f$e61a9be0$b24fd3a0$%han@samsung.com' \
    --to=jg1.han@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=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;
as well as URLs for NNTP newsgroup(s).