From: r.herring@freescale.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 08/10] imx: Add MX53 core support
Date: Fri, 23 Apr 2010 16:02:25 -0500 [thread overview]
Message-ID: <1272056545.20896.58.camel@ra7055-linux> (raw)
In-Reply-To: <20100423193709.GB18310@pengutronix.de>
Uwe,
On Fri, 2010-04-23 at 12:37 -0700, Uwe Kleine-K?nig wrote:
> all in all this looks like a sort of minimal change to make it work
> (which is good), but it destroys the efforts spend in the past to use
> proper name spaces and have understandable, modular and easy code. So
> according to my preferences about how to program the patch is wrong.
>
Thanks for you comments. The minimal change was the whole point and why
it is just RFC. I wanted input before going any further. It seems a bit
pointless to me to create devices-mx53.c, clock-mx53.c, etc. all for a
simple shift in register base.
Rob
prev parent reply other threads:[~2010-04-23 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 19:35 [RFC PATCH 08/10] imx: Add MX53 core support Rob Herring
2010-04-18 2:35 ` Sascha Hauer
2010-04-19 14:53 ` Herring Robert-RA7055
2010-04-23 19:26 ` Uwe Kleine-König
2010-04-23 19:37 ` Uwe Kleine-König
2010-04-23 21:02 ` Rob Herring [this message]
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=1272056545.20896.58.camel@ra7055-linux \
--to=r.herring@freescale.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).