From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: G4EVM KEYSC platform data
Date: Wed, 24 Feb 2010 00:51:33 +0000 [thread overview]
Message-ID: <20100224005133.GA17581@linux-sh.org> (raw)
In-Reply-To: <4B83B40E.5040203@renesas.com>
On Wed, Feb 24, 2010 at 09:03:38AM +0900, Kuninori Morimoto wrote:
> > @@ -82,6 +87,8 @@ static struct clk_lookup lookups[] = {
> > .clk = &r_clk,
> > }, {
> > .clk = &usb0_clk,
> > + }, {
> > + .clk = &keysc0_clk,
> > }
> > };
>
> I think above settings are already done on Magnus's patch
>
> Subject: [PATCH] ARM: mach-shmobile: G3EVM KEYSC platform data
>
> This patch still isn't applied though =)
>
It is blocked on changes from the input tree. I usually do at least two
merges doing the merge window, so I'll roll this in with the second
bunch once the merge dependencies have been resolved.
prev parent reply other threads:[~2010-02-24 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 10:55 [PATCH] ARM: mach-shmobile: G4EVM KEYSC platform data NISHIMOTO Hiroki
2010-02-24 0:03 ` Kuninori Morimoto
2010-02-24 0:51 ` 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=20100224005133.GA17581@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).