From: Thomas Renninger <trenn@suse.de>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.33-rc6 - BUG at drivers/cpufreq/cpufreq.c:88
Date: Fri, 5 Feb 2010 10:26:32 +0100 [thread overview]
Message-ID: <201002051026.33057.trenn@suse.de> (raw)
In-Reply-To: <6843.1265299202@localhost>
On Thursday 04 February 2010 17:00:02 Valdis.Kletnieks@vt.edu wrote:
> Hit this one again while setting up to bisect another issue. I've verified
> that the fix *is* someplace in 2.6.33-rc6-mmotm0201 (as that one lives at least
> all the way to single-user mode), so I'm basically asking that somebody find
> the commit that fixes it and make sure it gets into 2.6.33-final. I'd offer
> the commit number for the fix, but I'm hoping somebody recognizes it and pushes
> it so I don't have bisect to find the fixing commit.
>
> Thomas? Did you have a fix for this that hasn't been pulled by Linus yet?
The fix is to remove the patch.
> Refresher: The bad commit was:
>
> commit 46aeb7430f79cb4d03e17fedd6399884ab3aa697
> Author: Thomas Renninger <trenn@suse.de>
> Date: Mon Dec 14 11:44:11 2009 +0100
>
> [CPUFREQ] Fix race in cpufreq_update_policy()
This one never hit Linus tree?
It was in -mm, but got reverted.
Did you bisect on another tree?
Thomas
PS: I checked by:
> cat .git/FETCH_HEAD
fc76be434d90bcd57a0ea6b93a2e66a3fec4b664 branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
> git pull
Already up-to-date.
> git branch
* master
> git show 46aeb7430f79cb4d03e17fedd6399884ab3aa697
fatal: bad object 46aeb7430f79cb4d03e17fedd6399884ab3aa697
next prev parent reply other threads:[~2010-02-05 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 16:00 2.6.33-rc6 - BUG at drivers/cpufreq/cpufreq.c:88 Valdis.Kletnieks
2010-02-05 9:26 ` Thomas Renninger [this message]
2010-02-08 17:25 ` Valdis.Kletnieks
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=201002051026.33057.trenn@suse.de \
--to=trenn@suse.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.