From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: G3EVM FLCTL platform data
Date: Thu, 20 May 2010 03:36:01 +0000 [thread overview]
Message-ID: <20100520033601.GG6661@linux-sh.org> (raw)
In-Reply-To: <20100219095406.5206.86934.sendpatchset@t400s>
On Tue, Feb 23, 2010 at 02:49:46PM +0900, Magnus Damm wrote:
> On Mon, Feb 22, 2010 at 7:31 PM, Paul Mundt <lethal@linux-sh.org> wrote:
> >> + ? ? /* FOE, FCDE, FSC on dedicated pins */
> >> + ? ? __raw_writel(__raw_readl(0xe6158048) & ~(1 << 15), 0xe6158048);
> >> +
> > This looks suspiciously like an obfuscated MSTP toggle that the clock
> > framework needs to be handling. I thought I was already pretty clear when
> > I said I wouldn't be applying any more of these sorts of patches until
> > some basic clock framework support was in place?
>
> I didn't ask you to apply the patch, just wanted to post it so other
> people can get the code.
>
I suppose you are going to respin this once the G3 clkdev stuff is
posted?
prev parent reply other threads:[~2010-05-20 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 9:54 [PATCH] ARM: mach-shmobile: G3EVM FLCTL platform data Magnus Damm
2010-02-22 10:31 ` Paul Mundt
2010-02-23 5:49 ` Magnus Damm
2010-05-20 3:36 ` 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=20100520033601.GG6661@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).