From: viresh kumar <viresh.kumar2@arm.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: viresh kumar <viresh.linux@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Sascha Hauer <s.hauer@pengutronix.de>,
spear-devel <spear-devel@list.st.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: "clk: add non CONFIG_HAVE_CLK routines" commit
Date: Tue, 12 Jun 2012 12:13:23 +0100 [thread overview]
Message-ID: <4FD72453.1040602@arm.com> (raw)
In-Reply-To: <20120612110929.GA16511@localhost>
On 12/06/12 12:09, Fengguang Wu wrote:
> Another thing I'm not sure is that the typical clk_get() callers only
> tests IS_ERR() on the returned value. As a clk newbie, I don't know
> whether there will be lots of clk users seeing this (new) NULL value
> on !CONFIG_HAVE_CLK and whether the current behavior is correct..
There have been long discussions over it in past, check this thread
https://lkml.org/lkml/2012/4/24/389
--
Viresh
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2012-06-12 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 23:46 "clk: add non CONFIG_HAVE_CLK routines" commit Paul Gortmaker
2012-05-25 9:37 ` [linux-next] " viresh kumar
2012-06-12 10:57 ` viresh kumar
2012-06-12 11:09 ` Fengguang Wu
2012-06-12 11:13 ` viresh kumar [this message]
2012-06-12 14:08 ` Russell King - ARM Linux
2012-06-12 14:21 ` [linux-next] " viresh kumar
2012-06-13 22:10 ` Sascha Hauer
2012-06-14 10:04 ` Russell King - ARM Linux
2012-06-14 10:18 ` Sascha Hauer
2012-06-14 10:21 ` viresh kumar
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=4FD72453.1040602@arm.com \
--to=viresh.kumar2@arm.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul.gortmaker@windriver.com \
--cc=s.hauer@pengutronix.de \
--cc=spear-devel@list.st.com \
--cc=viresh.linux@gmail.com \
/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).