From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP: hwmod: align the SmartReflex fck names
Date: Tue, 02 Oct 2012 15:08:00 -0700 [thread overview]
Message-ID: <506B65C0.7070902@deeprootsystems.com> (raw)
In-Reply-To: <87626s8rys.fsf@deeprootsystems.com>
On 10/02/2012 02:49 PM, Kevin Hilman wrote:
> Jean Pihet <jean.pihet@newoldbits.com> writes:
>
>> Rename the smartreflex fck names for consistency and better readability;
>> rename the clock aliases for use by the SmartReflex driver, with the
>> "smartreflex.%d" format.
>
> hmm, do we even need the clkdev nodes anymore? The driver isn't
> directly accessing the fclk at all, so it seems like these could be
> removed now.
Please ignore this comment, I see what you're doing in the other series
now. See my comments there.
Kevin
prev parent reply other threads:[~2012-10-02 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 9:48 [PATCH] ARM: OMAP: hwmod: align the SmartReflex fck names Jean Pihet
2012-09-24 14:34 ` Jean Pihet
2012-09-24 14:35 ` Jean Pihet
2012-10-02 21:49 ` Kevin Hilman
2012-10-02 22:08 ` Kevin Hilman [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=506B65C0.7070902@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.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).