From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/6] Add support for SH7724 CPU subtype
Date: Tue, 14 Apr 2009 09:17:22 +0000 [thread overview]
Message-ID: <20090414091721.GA30402@linux-sh.org> (raw)
On Tue, Apr 14, 2009 at 05:14:39PM +0900, Kuninori Morimoto wrote:
> This adds preliminary support for the SH7724 CPU subtype.
> This patch is based on Rev 0.11 manual
>
> Signed-off-by: Kuninori Morimoto <morimoto.kuninori@renesas.com>
Please resend this patch series with the timestamps corrected and
properly nested. They are not only completely out of order, but do not
nest at all. Even if you just have a 0/6 mail that summarizes the patch
set and all of the other patches nest under that, it makes it a lot
easier to figure out where things are supposed to go.
reply other threads:[~2009-04-14 9:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090414091721.GA30402@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox