From: Fengguang Wu <fengguang.wu@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [cpufreq] WARNING: at kernel/lockdep.c:2739 lockdep_trace_alloc()
Date: Mon, 11 Feb 2013 21:08:00 +0800 [thread overview]
Message-ID: <20130211130800.GA16039@localhost> (raw)
In-Reply-To: <CAKohpo=WRgdBUfzKrs7yeNDCgT6w+j7GPFr8QfbPOShdGgEd1w@mail.gmail.com>
On Mon, Feb 11, 2013 at 02:40:39PM +0530, Viresh Kumar wrote:
> On 11 February 2013 14:22, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > Greetings,
>
> Hi Fengguang,
>
> > I got the below oops and the first bad commit is
> >
> > commit 50f6802f8dccb7bbad29010e57973d46b7e7a07e
> > Author: Viresh Kumar <viresh.kumar@linaro.org>
> > Date: Thu Feb 7 10:55:00 2013 +0530
>
> There is something really wrong. This problem was earlier reported
> and was fixed immediately. And shouldn't be there with linux-next
> branch of Rafael.
>
> What tree are you working on ?
>
> Even in linux-next/master i see above commit as:
>
> commit 2eaa3e2df185997e92596ab14a2a67dde3876d2e
> Author: Viresh Kumar <viresh.kumar@linaro.org>
> Date: Thu Feb 7 10:55:00 2013 +0530
>
> cpufreq: Fix locking issues
Viresh, I confirmed that the updated commit is fine. Sorry for the noise!
Fengguang
prev parent reply other threads:[~2013-02-11 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 8:52 [cpufreq] WARNING: at kernel/lockdep.c:2739 lockdep_trace_alloc() Fengguang Wu
2013-02-11 9:10 ` Viresh Kumar
2013-02-11 13:08 ` Fengguang Wu [this message]
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=20130211130800.GA16039@localhost \
--to=fengguang.wu@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).