From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org, Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: next-20130206 cpufreq - WARN in sysfs_add_one
Date: Thu, 07 Feb 2013 03:03:01 +0100 [thread overview]
Message-ID: <40027556.U5lg3c4VjV@vostro.rjw.lan> (raw)
In-Reply-To: <1729273.hgXged98n0@vostro.rjw.lan>
On Thursday, February 07, 2013 02:12:17 AM Rafael J. Wysocki wrote:
> On Wednesday, February 06, 2013 07:55:58 PM Valdis.Kletnieks@vt.edu wrote:
> > On Wed, 06 Feb 2013 22:24:39 +0100, "Rafael J. Wysocki" said:
> > > On Wednesday, February 06, 2013 12:44:35 PM Valdis Kletnieks wrote:
> > > > Seen in dmesg. next-20130128 was OK. Haven't done a bisect, but can
> > > > do so if the offender isn't obvious...
> > >
> > > I suppose this is 73bf0fc "cpufreq: Don't remove sysfs link for policy->cpu".
> > >
> > > Can you test the linux-pm.git/pm-cpufreq branch alone, please, and see
> > > if that's this one (top-most commit)?
> >
> > Color me mystified. I can't find that commit by either number or
> > the description:
> >
> > [/usr/src/linux-next] git log | egrep -i 'cpufreq.*remove.*link'
> > [/usr/src/linux-next] git log | grep -i 73bf0fc
> > [/usr/src/linux-next]
> >
> > Was that a very recent commit that may have gotten pushed too late
> > for the next-20130206 merge?
>
> Well, sorry, next-20130206 didn't include that commit.
>
> Can you please test the linux-pm.git/pm-cpufreq branch, then?
To be precise, I mean the pm-cpufreq branch of the tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
which is based on v3.8-rc6.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-02-07 1:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 17:44 Valdis Kletnieks
2013-02-06 21:24 ` Rafael J. Wysocki
2013-02-07 0:55 ` Valdis.Kletnieks
2013-02-07 1:12 ` Rafael J. Wysocki
2013-02-07 2:03 ` Rafael J. Wysocki [this message]
2013-02-07 7:41 ` Viresh Kumar
2013-02-07 19:18 ` Valdis.Kletnieks
2013-02-08 2:45 ` Viresh Kumar
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=40027556.U5lg3c4VjV@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=Valdis.Kletnieks@vt.edu \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®