From: Kevin Hilman <khilman@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: Stop BUGing the system
Date: Wed, 17 Dec 2014 11:16:36 -0800 [thread overview]
Message-ID: <7hoar29je3.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1418831495-26958-1-git-send-email-nm@ti.com> (Nishanth Menon's message of "Wed, 17 Dec 2014 09:51:35 -0600")
Nishanth Menon <nm@ti.com> writes:
> CPUFRreq subsystem is not a system catastrophic failure point.
> Failures in these cases DONOT need complete system shutdown with BUG.
> just refuse to let cpufreq function should be good enough.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Acked-by: Kevin Hilman <khilman@linaro.org>
next prev parent reply other threads:[~2014-12-17 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 15:51 [PATCH] cpufreq: Stop BUGing the system Nishanth Menon
2014-12-17 19:16 ` Kevin Hilman [this message]
2014-12-18 2:08 ` Viresh Kumar
2014-12-18 14:49 ` Nishanth Menon
2014-12-19 1:41 ` Viresh Kumar
2014-12-19 2:08 ` Rafael J. Wysocki
2014-12-24 15:06 ` Nishanth Menon
2014-12-27 20:37 ` 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=7hoar29je3.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox