From: Dave Jones <davej@redhat.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUGFIX] cpufreq: dont BUG_ON uninitialized policy cpu
Date: Wed, 13 Jan 2010 10:59:06 -0500 [thread overview]
Message-ID: <20100113155905.GA1965@redhat.com> (raw)
In-Reply-To: <4B4DBFBC.4090400@suse.de>
On Wed, Jan 13, 2010 at 01:42:36PM +0100, Thomas Renninger wrote:
> On 01/13/2010 06:14 AM, Wu Fengguang wrote:
> > Remove a BUG_ON which is always triggered here after commit 0b19a310eebb93:
> The patch got dropped from -mm.
> I hope it did not make it upstream yet, otherwise it should also
> get dropped/reverted there without replacement.
> There wasn't a real, only a theoretical issue.
> Looking at it again, I now think it's not needed at all.
dropped from cpufreq.git
I'm still curious how we're calling cpufreq_update_policy with no policy set.
I suspect cpufreq_stats might be doing something wrong.
Dave
next prev parent reply other threads:[~2010-01-13 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 5:14 [BUGFIX] cpufreq: dont BUG_ON uninitialized policy cpu Wu Fengguang
2010-01-13 6:32 ` Dave Jones
2010-01-13 12:42 ` Thomas Renninger
2010-01-13 12:48 ` Wu Fengguang
2010-01-13 15:59 ` Dave Jones [this message]
2010-01-14 2:42 ` Wu Fengguang
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=20100113155905.GA1965@redhat.com \
--to=davej@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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