From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: RSK+ 7201 board support
Date: Fri, 28 Nov 2008 14:09:02 +0000 [thread overview]
Message-ID: <20081128140902.GC18785@linux-sh.org> (raw)
In-Reply-To: <492EA011.40707@mpc-data.co.uk>
On Fri, Nov 28, 2008 at 12:43:36PM +0000, Peter Griffin wrote:
> Hi Paul,
>
> Paul Mundt wrote:
> >On Thu, Nov 27, 2008 at 01:26:41PM +0000, Peter Griffin wrote:
> >>From: Peter Griffin <pgriffin@mpc-data.co.uk>
> >>
> >>sh: RSK+ 7201 board support
> >>
> >>This patch adds support for the SH7201 processor subtype and RSK+ 7201
> >>board.
> >>
> >>Signed-off-by: Peter Griffin <pgriffin@mpc-data.co.uk>
> >
> >Just a couple minor nits. I would prefer if you would send the CPU and
> >the board support separately, so I don't have to try and split the patch
> >up manually. Additionally, as far as new boards go, you should also
> >provide a reasonable defconfig so that we can tie it in to the nightly
> >builds and make sure no one ends up breaking it.
>
> I've posted three more patches with the board and cpu stuff seperated out.
> The third is a default kernel config. Is that ok?
>
Yes, that is fine. You missed a couple of places where the subtype and
board type should be wired in, but I just added those by hand.
Also, your patches were heavily whitespace damaged, so it took a bit of
wiggling to get them to even apply. Next time, please double check your
mailer settings.
I have now applied all of the patches. Looking at the board support
itself, it seems like the 7201 rsk and the 7203 rsk have a lot of
similarities. I have not looked at the schematics or the datasheet for
the board yet, so I am not aware of all of the differences between the
two platforms, but the fact everything you have in board-rsk7201.c is
identical to the rsk7203 (with the exception of ethernet and GPIOs being
ripped out) suggests that this is something that should be rolled in to a
mach-rsk in order to avoid needless duplication. This is something that
can be done incrementally though, as the current implementation is
sufficiently trivial.
next prev parent reply other threads:[~2008-11-28 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 13:26 [PATCH] sh: RSK+ 7201 board support Peter Griffin
2008-11-27 20:13 ` Paul Mundt
2008-11-28 12:43 ` Peter Griffin
2008-11-28 14:09 ` Paul Mundt [this message]
2008-12-01 11:07 ` Peter Griffin
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=20081128140902.GC18785@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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.