All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Kukjin Kim <kgene.kim@samsung.com>, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 0/7] ARM: S5P: moving plat-s5p stuff into plat-samsung
Date: Thu, 19 Apr 2012 13:23:32 +0000	[thread overview]
Message-ID: <201204191323.32301.arnd@arndb.de> (raw)
In-Reply-To: <1334802036-16768-1-git-send-email-kgene.kim@samsung.com>

On Thursday 19 April 2012, Kukjin Kim wrote:
> This patches move plat-s5p stuff into plat-samsung for keep just one
> plat directory, plat-samsung for Samsung stuff. Actually, it includes
> small things for common s5p and there is no problem this moving.
> Of course, I'm working on removing plat-s3c24xx and will be submitted
> before v3.4 release.
> 
> NOTE, now the plat-s5p directory which is including Kconfig and dummy
> Makefile is not removed yet because need to cleanup CONFIG_PLAT_S5P
> and will be removed soon.
> 

Very nice!

Out of curiosity, how far are you planning to take the consolidation
of the various directories in the end?
I assume all the s3c24* directories end up getting merged into
s3c24xx, but what about s3c64xx, s5p64x0, s5pc100 and s5pcv210?
Are they going to stay separate or do they get merged together
or with exynos?

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] ARM: S5P: moving plat-s5p stuff into plat-samsung
Date: Thu, 19 Apr 2012 13:23:32 +0000	[thread overview]
Message-ID: <201204191323.32301.arnd@arndb.de> (raw)
In-Reply-To: <1334802036-16768-1-git-send-email-kgene.kim@samsung.com>

On Thursday 19 April 2012, Kukjin Kim wrote:
> This patches move plat-s5p stuff into plat-samsung for keep just one
> plat directory, plat-samsung for Samsung stuff. Actually, it includes
> small things for common s5p and there is no problem this moving.
> Of course, I'm working on removing plat-s3c24xx and will be submitted
> before v3.4 release.
> 
> NOTE, now the plat-s5p directory which is including Kconfig and dummy
> Makefile is not removed yet because need to cleanup CONFIG_PLAT_S5P
> and will be removed soon.
> 

Very nice!

Out of curiosity, how far are you planning to take the consolidation
of the various directories in the end?
I assume all the s3c24* directories end up getting merged into
s3c24xx, but what about s3c64xx, s5p64x0, s5pc100 and s5pcv210?
Are they going to stay separate or do they get merged together
or with exynos?

	Arnd

  parent reply	other threads:[~2012-04-19 13:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19  2:20 [PATCH 0/7] ARM: S5P: moving plat-s5p stuff into plat-samsung Kukjin Kim
2012-04-19  2:20 ` Kukjin Kim
2012-04-19  2:20 ` [PATCH 1/7] ARM: SAMSUNG: move clock part for common s5p " Kukjin Kim
2012-04-19  2:20   ` Kukjin Kim
2012-04-19  2:20 ` [PATCH 2/7] ARM: SAMSUNG: move interrupt " Kukjin Kim
2012-04-19  2:20   ` Kukjin Kim
2012-04-19  2:20 ` [PATCH 3/7] ARM: SAMSUNG: move pm " Kukjin Kim
2012-04-19  2:20   ` Kukjin Kim
2012-04-19  2:20 ` [PATCH 4/7] ARM: SAMSUNG: move hr timer " Kukjin Kim
2012-04-19  2:20   ` Kukjin Kim
2012-04-19  2:20 ` [PATCH 5/7] ARM: SAMSUNG: move platform device for s5p uart " Kukjin Kim
2012-04-19  2:20   ` Kukjin Kim
2012-04-19  2:20 ` [PATCH 6/7] ARM: SAMSUNG: move setup code for s5p mfc and mipiphy " Kukjin Kim
2012-04-19  2:20   ` Kukjin Kim
2012-04-19  2:20 ` [PATCH 7/7] ARM: SAMSUNG: move options for common s5p into plat-samsung/Kconfig Kukjin Kim
2012-04-19  2:20   ` Kukjin Kim
2012-04-19 13:23 ` Arnd Bergmann [this message]
2012-04-19 13:23   ` [PATCH 0/7] ARM: S5P: moving plat-s5p stuff into plat-samsung Arnd Bergmann
2012-04-25  0:16   ` Kukjin Kim
2012-04-25  0:16     ` 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=201204191323.32301.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.