linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: m.szyprowski@samsung.com (Marek Szyprowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Samsung: Add platform support code for OneNAND controller
Date: Thu, 20 May 2010 11:33:30 +0200	[thread overview]
Message-ID: <014f01caf7ff$84d456f0$8e7d04d0$%szyprowski@samsung.com> (raw)
In-Reply-To: <20100520084848.GO4720@trinity.fluff.org>

Hello,

On Thursday, May 20, 2010 10:49 AM Ben Dooks wrote:

> On Thu, May 20, 2010 at 08:59:05AM +0200, Marek Szyprowski wrote:
> > This patch adds setup code for Samsung OneNAND controller driver. The
> > driver needs to be aware on which SoC it is running, so the actual
> > device id is being changed in cpu init code. S3C64xx SoCs have 2 OneNAND
> > controllers while S5PC100 and S5PC110 has only one.
> >
> > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> 
> Ok, in future please try and keep a core and then have the architecture
> additions seperate, it makes it very difficult to deal with any problems
> whilst merging and means there is a higher possibility of a problem during
> this.

Ok, but I'm still not 100% sure how should I handle case like this properly.
I thought that separating platform files from the driver itself would help
merging it, because each part (the driver and platform setup code/register
definitions) can be merged separately by the respective maintainers. Was it
wrong that the platform patch was prepared for the tree after plat-s5pc1xx
moves? 

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

  reply	other threads:[~2010-05-20  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20  6:59 [PATCH] ARM: Samsung: Add platform support code for OneNAND controller Marek Szyprowski
2010-05-20  8:48 ` Ben Dooks
2010-05-20  9:33   ` Marek Szyprowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-09  6:46 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='014f01caf7ff$84d456f0$8e7d04d0$%szyprowski@samsung.com' \
    --to=m.szyprowski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.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).