From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: modify pinmux for SH7757 2nd cut
Date: Fri, 07 May 2010 11:34:54 +0000 [thread overview]
Message-ID: <20100507113453.GA14948@linux-sh.org> (raw)
In-Reply-To: <4BE3DC84.4070203@renesas.com>
On Fri, May 07, 2010 at 08:24:46PM +0900, Yoshihiro Shimoda wrote:
> Paul Mundt wrote:
> > If the 1st cut has already shipped, then the 2nd cut will have to be
> > added as a new CPU by itself. We managed to dodge this bullet for 7786 at
> > least by never supporting the 90nm version, but we would have obviously
> > been in the same situation there as well of adding a new CPU subtype to
> > account for the lack of consistency between silicon revisions.
>
> Thank you very much for your comment.
> I will ask my boss about this plan.
> Would you wait to apply the today's patches?
>
The serial one shouldn't matter one way or the other, but if you're
planning on respinning the series then of course I can just deal with
that then as well.
prev parent reply other threads:[~2010-05-07 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 9:25 [PATCH] sh: modify pinmux for SH7757 2nd cut Yoshihiro Shimoda
2010-05-07 9:29 ` Paul Mundt
2010-05-07 10:15 ` Yoshihiro Shimoda
2010-05-07 10:32 ` Paul Mundt
2010-05-07 11:24 ` Yoshihiro Shimoda
2010-05-07 11:34 ` Paul Mundt [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=20100507113453.GA14948@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;
as well as URLs for NNTP newsgroup(s).