linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* S5PC100 planning
@ 2010-05-13  4:25 Ben Dooks
  2010-05-13 10:02 ` Kukjin Kim
  0 siblings, 1 reply; 3+ messages in thread
From: Ben Dooks @ 2010-05-13  4:25 UTC (permalink / raw)
  To: linux-arm-kernel

I would like to get an idea of what each group involvedi n the
current S5PC100 changes is planning to allow the organisation of
what is going on.

Firstly, I think Kukjin's clock changes are the first to be
applied, followed by looking at what support exists (or is being
submitted) in plat-s5p which could be used for s5pc100.

Then, let's move out what is left of plat-s5pc1xx into mach-s5pc100
and get rid of it (although the final removal may have to be left
until the next merge window, due to time constraints).

I would like to see whatever changes done grouped into sections,
such as clock, machine, core, gpio.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* S5PC100 planning
  2010-05-13  4:25 S5PC100 planning Ben Dooks
@ 2010-05-13 10:02 ` Kukjin Kim
  2010-05-13 11:11   ` Marek Szyprowski
  0 siblings, 1 reply; 3+ messages in thread
From: Kukjin Kim @ 2010-05-13 10:02 UTC (permalink / raw)
  To: linux-arm-kernel

Ben Dooks wrote:
> 
> I would like to get an idea of what each group involvedi n the
> current S5PC100 changes is planning to allow the organisation of
> what is going on.
> 
> Firstly, I think Kukjin's clock changes are the first to be
> applied, followed by looking at what support exists (or is being
> submitted) in plat-s5p which could be used for s5pc100.
> 
> Then, let's move out what is left of plat-s5pc1xx into mach-s5pc100
> and get rid of it (although the final removal may have to be left
> until the next merge window, due to time constraints).
> 
> I would like to see whatever changes done grouped into sections,
> such as clock, machine, core, gpio.

I will re-submit S5PC100 clock patch which can be merged to Ben's latest tree
without any compile error.

Marek, can you re-make your patches based on it?

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* S5PC100 planning
  2010-05-13 10:02 ` Kukjin Kim
@ 2010-05-13 11:11   ` Marek Szyprowski
  0 siblings, 0 replies; 3+ messages in thread
From: Marek Szyprowski @ 2010-05-13 11:11 UTC (permalink / raw)
  To: linux-arm-kernel

Hello,

On Thursday, May 13, 2010 12:02 PM Kukjin Kim wrote:

> Ben Dooks wrote:
> >
> > I would like to get an idea of what each group involvedi n the
> > current S5PC100 changes is planning to allow the organisation of
> > what is going on.
> >
> > Firstly, I think Kukjin's clock changes are the first to be
> > applied, followed by looking at what support exists (or is being
> > submitted) in plat-s5p which could be used for s5pc100.
> >
> > Then, let's move out what is left of plat-s5pc1xx into mach-s5pc100
> > and get rid of it (although the final removal may have to be left
> > until the next merge window, due to time constraints).
> >
> > I would like to see whatever changes done grouped into sections,
> > such as clock, machine, core, gpio.
> 
> I will re-submit S5PC100 clock patch which can be merged to Ben's latest
> tree
> without any compile error.
> 
> Marek, can you re-make your patches based on it?

Yes, I will do this soon.

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-05-13 11:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-13  4:25 S5PC100 planning Ben Dooks
2010-05-13 10:02 ` Kukjin Kim
2010-05-13 11:11   ` Marek Szyprowski

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).