From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Axel Lin <axel.lin@gmail.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: OMAP: Check IS_ERR() instead of NULL for omap_device_get_by_hwmod_name
Date: Wed, 19 Sep 2012 09:51:35 -0700 [thread overview]
Message-ID: <877grqj6qw.fsf@deeprootsystems.com> (raw)
In-Reply-To: <201209182052.57414.rjw@sisk.pl> (Rafael J. Wysocki's message of "Tue, 18 Sep 2012 20:52:57 +0200")
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
> On Tuesday, September 18, 2012, Axel Lin wrote:
>> omap_device_get_by_hwmod_name() returns ERR_PTR on error.
>>
>> Signed-off-by: Axel Lin <axel.lin@gmail.com>
>
> Kevin, should I take this?
Yes, please.
Acked-by: Kevin Hilman <khilman@ti.com>
Thanks,
Kevin
next prev parent reply other threads:[~2012-09-19 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 1:45 [PATCH] cpufreq: OMAP: Check IS_ERR() instead of NULL for omap_device_get_by_hwmod_name Axel Lin
2012-09-18 18:52 ` Rafael J. Wysocki
2012-09-19 16:51 ` Kevin Hilman [this message]
2012-09-19 20:17 ` Rafael J. Wysocki
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=877grqj6qw.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=axel.lin@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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