All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: 'Ben Dooks' <ben-linux@fluff.org>,
	linux-arm-kernel@lists.infradead.org,
	'Linux Samsung SoC' <linux-samsung-soc@vger.kernel.org>
Cc: 'Kyungmin Park' <kmpark@infradead.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: RE: S5PC100 squashing
Date: Tue, 26 Jan 2010 10:25:32 +0100	[thread overview]
Message-ID: <000001ca9e69$85087880$8f196980$%szyprowski@samsung.com> (raw)
In-Reply-To: <20100126083201.GZ10014@trinity.fluff.org>

Hello,

On Tuesday, January 26, 2010 9:32 AM Ben Dooks wrote:

> Does anyone have any opinion on whether plat-s5pc1xx should stay? At the
> moment it is only servicing mach-s5pc100 and thenew support for v210 and
> s5pc110 seem to be using plat-s5p and not plat-s5pc1xx.

I vote for moving s5pc100 support to plat-s5p directory and removing
plat-s5pc1xx dir completely. I want to prepare patches for this, but
waited until S5PV210 support gets merged.

> From the looks of it, s5pc100-init.c could probably be pushed into
> the arch/arm/mach-s5pc100/cpu.c file. The s5pc100-clock.c should be
> moved into arch/arm/mach-s5pc100/ as well.

Right.

> Not sure yet what to do with the rest.

Most of c100-specific code should be moved to mach-s5pc100 directory.
The rest can be probably shared with all S5P platforms. 

Best regards
--
Marek Szyprowski
Samsung Poland R&D Center

WARNING: multiple messages have this Message-ID (diff)
From: m.szyprowski@samsung.com (Marek Szyprowski)
To: linux-arm-kernel@lists.infradead.org
Subject: S5PC100 squashing
Date: Tue, 26 Jan 2010 10:25:32 +0100	[thread overview]
Message-ID: <000001ca9e69$85087880$8f196980$%szyprowski@samsung.com> (raw)
In-Reply-To: <20100126083201.GZ10014@trinity.fluff.org>

Hello,

On Tuesday, January 26, 2010 9:32 AM Ben Dooks wrote:

> Does anyone have any opinion on whether plat-s5pc1xx should stay? At the
> moment it is only servicing mach-s5pc100 and thenew support for v210 and
> s5pc110 seem to be using plat-s5p and not plat-s5pc1xx.

I vote for moving s5pc100 support to plat-s5p directory and removing
plat-s5pc1xx dir completely. I want to prepare patches for this, but
waited until S5PV210 support gets merged.

> From the looks of it, s5pc100-init.c could probably be pushed into
> the arch/arm/mach-s5pc100/cpu.c file. The s5pc100-clock.c should be
> moved into arch/arm/mach-s5pc100/ as well.

Right.

> Not sure yet what to do with the rest.

Most of c100-specific code should be moved to mach-s5pc100 directory.
The rest can be probably shared with all S5P platforms. 

Best regards
--
Marek Szyprowski
Samsung Poland R&D Center

  reply	other threads:[~2010-01-26  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26  8:32 S5PC100 squashing Ben Dooks
2010-01-26  8:32 ` Ben Dooks
2010-01-26  9:25 ` Marek Szyprowski [this message]
2010-01-26  9:25   ` Marek Szyprowski

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='000001ca9e69$85087880$8f196980$%szyprowski@samsung.com' \
    --to=m.szyprowski@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=kmpark@infradead.org \
    --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.