From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Yinghai Lu <yinghai@kernel.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: return EEXIST instead of EBUSY for second registering
Date: Fri, 20 Sep 2013 00:37:50 +0200 [thread overview]
Message-ID: <11319698.mBBnJVdnIk@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpomt+sASL=2i-v=HSkhOZhbPmnFesEfPoEqSE+WKcCfnmw@mail.gmail.com>
On Thursday, September 19, 2013 09:38:32 AM Viresh Kumar wrote:
> On 19 September 2013 09:35, Yinghai Lu <yinghai@kernel.org> wrote:
> > System that cpu support intel_pstate, acpi_cpufreq fail to
> > load, and udev keep trying until trace get filled up and
> > kernel crash.
> >
> > The root cause is driver return ret from cpufreq_register_driver
> > and when some other driver take over before, it would return
> > EBUSY, then udev will keep trying...
> >
> > cpufreq_register_driver should return EEXIST instead.
> > then system could boot without appending intel_pstate=disable
> > and still use intel_pstate.
> >
> > Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-09-19 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 4:05 Yinghai Lu
2013-09-19 4:08 ` Viresh Kumar
2013-09-19 22:37 ` Rafael J. Wysocki [this message]
2013-09-20 1:31 ` Yinghai Lu
2013-09-20 4:23 ` Viresh Kumar
2013-09-20 5:30 ` Yinghai Lu
2013-09-20 13:30 ` Rafael J. Wysocki
2013-09-20 17:12 ` Yinghai Lu
2013-09-20 19:30 ` Yinghai Lu
2013-09-20 20:16 ` 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=11319698.mBBnJVdnIk@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=yinghai@kernel.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
all inboxes | Powered by JetHome®