From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Jon Medhurst (Tixy)" <tixy@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] cpufreq: Properly handle errors from cpufreq_init_policy()
Date: Wed, 8 Jul 2015 16:50:23 +0530 [thread overview]
Message-ID: <20150708112023.GE1805@linux> (raw)
In-Reply-To: <1436354276.2844.20.camel@linaro.org>
On 08-07-15, 12:17, Jon Medhurst (Tixy) wrote:
> I tried these patches without the earlier "cpufreq: Initialize the
> governor again while restoring policy" patch.
>
> The result is that the error when bringing a cpu online is with flagged
> up with a kernel message:
>
> cpufreq: cpufreq_add_dev: Failed to initialize policy for cpu: 1 (-16)
>
> and afterwards, the sysfs entries that I was poking and causing the
> crash aren't present. So looks like this patch has done what we want,
> and cleaned things up after an error. So...
>
> Tested-by: Jon Medhurst <tixy@linaro.org>
>
> Thanks for the prompt fix.
And thanks for your help in getting these tested :)
--
viresh
next prev parent reply other threads:[~2015-07-08 11:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 9:42 [PATCH 1/2] cpufreq: cpufreq_add_dev: name goto labels based on what they do Viresh Kumar
2015-07-08 9:42 ` Viresh Kumar
2015-07-08 9:42 ` [PATCH 2/2] cpufreq: Properly handle errors from cpufreq_init_policy() Viresh Kumar
2015-07-08 9:42 ` Viresh Kumar
2015-07-08 11:17 ` Jon Medhurst (Tixy)
2015-07-08 11:20 ` Viresh Kumar [this message]
2015-07-16 0:32 ` Rafael J. Wysocki
2015-07-16 9:16 ` Jon Medhurst (Tixy)
2015-07-16 23:07 ` 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=20150708112023.GE1805@linux \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tixy@linaro.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.