Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Tushar Behera <tushar.behera-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Jingoo Han <jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: 'Kukjin Kim' <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
	linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	'Greg Kroah-Hartman' <gregkh-l3A5Bk7waGM@public.gmane.org>,
	'Alan Stern'
	<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
	'Yulgon Kim' <yulgon.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH v2 1/3] ARM: EXYNOS: Add USB OHCI device
Date: Tue, 06 Dec 2011 14:43:15 +0530	[thread overview]
Message-ID: <4EDDDCAB.1000001@linaro.org> (raw)
In-Reply-To: <001301ccb3e0$b5fec280$21fc4780$%han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>

On Tuesday 06 December 2011 12:01 PM, Jingoo Han wrote:
> This patch adds USB ohci device definition for Exynos SoCs.
>
> Signed-off-by: Jingoo Han<jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> ---
>   arch/arm/mach-exynos/Kconfig              |    5 +++
>   arch/arm/mach-exynos/Makefile             |    1 +
>   arch/arm/mach-exynos/dev-ohci.c           |   52 +++++++++++++++++++++++++++++
>   arch/arm/mach-exynos/include/mach/map.h   |    1 +
>   arch/arm/mach-exynos/include/mach/ohci.h  |   21 +++++++++++

In the earlier patchset, platform_device struct for ohci was defined 
within plat-samsung, and ohci.h was located in 
plat-samsung/include/plat. These are still the locations where ehci 
related definitions are located.

What is the reason for movement of ohci related definitions to mach folder?

-- 
Tushar Behera
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-12-06  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06  6:30 [PATCH v2 0/3] Support Samsung Exynos OHCI device and driver Jingoo Han
2011-12-06  6:31 ` [PATCH v2 1/3] ARM: EXYNOS: Add USB OHCI device Jingoo Han
     [not found]   ` <001301ccb3e0$b5fec280$21fc4780$%han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2011-12-06  9:13     ` Tushar Behera [this message]
     [not found]       ` <4EDDDCAB.1000001-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-12-06  9:30         ` Jingoo Han
2011-12-06  6:32 ` [PATCH v2 2/3] ARM: EXYNOS: Add USB OHCI support to SMDKV310 board Jingoo Han
2011-12-06  6:32 ` [PATCH v2 3/3] USB: Add Samsung Exynos OHCI diver 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=4EDDDCAB.1000001@linaro.org \
    --to=tushar.behera-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=gregkh-l3A5Bk7waGM@public.gmane.org \
    --cc=jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org \
    --cc=yulgon.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.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