From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] CLKDEV: Add helper routines to allocate and add clkdevs for given struct clk *
Date: Tue, 17 Apr 2012 09:10:14 +0530 [thread overview]
Message-ID: <4F8CE61E.9090504@st.com> (raw)
In-Reply-To: <20120416211232.GL20478@pengutronix.de>
On 4/17/2012 2:42 AM, s.hauer at pengutronix.de wrote:
>>> > > Can we drop the 'single' in the name? Otherwise it's quite a long
>>> > > function name. I think name clk_register_clkdev makes it clear already
>>> > > that we only register a single clkdev.
>> >
>> > clkdev_register?
> Maybe even this. I just though that it might be too easy to confuse with
> clkdev_add (In fact I think clkdev_register would be a good name for
> what clkdev_add currently does, but it's probably not worth the churn
> changing this).
I will keep clk_register_clkdev() and clk_register_clkdevs().
--
viresh
prev parent reply other threads:[~2012-04-17 3:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 5:19 [PATCH] CLKDEV: Add helper routines to allocate and add clkdevs for given struct clk * Viresh Kumar
2012-04-16 10:25 ` Domenico Andreoli
2012-04-16 10:30 ` Viresh Kumar
2012-04-16 10:38 ` Russell King - ARM Linux
2012-04-16 10:39 ` Viresh Kumar
2012-04-16 10:56 ` Domenico Andreoli
2012-04-16 10:58 ` Viresh Kumar
2012-04-16 11:02 ` Russell King - ARM Linux
2012-04-16 11:52 ` Domenico Andreoli
2012-04-16 13:39 ` viresh kumar
2012-04-16 20:46 ` Domenico Andreoli
2012-04-16 20:51 ` s.hauer at pengutronix.de
2012-04-17 3:39 ` Viresh Kumar
2012-04-17 3:48 ` [PATCH V3] " Viresh Kumar
2012-04-17 3:34 ` [PATCH] " Viresh Kumar
2012-04-16 20:56 ` s.hauer at pengutronix.de
2012-04-16 21:06 ` Domenico Andreoli
2012-04-16 21:12 ` s.hauer at pengutronix.de
2012-04-17 3:40 ` Viresh Kumar [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=4F8CE61E.9090504@st.com \
--to=viresh.kumar@st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.