From: Andrew Lunn <andrew@lunn.ch>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
viresh.kumar@linaro.org, linux-pm@vger.kernel.org
Subject: Re: cpufreq-next opps with cpufreq-bench
Date: Sun, 13 Oct 2013 23:45:47 +0200 [thread overview]
Message-ID: <20131013214547.GC24927@lunn.ch> (raw)
In-Reply-To: <20131013211436.GB24927@lunn.ch>
On Sun, Oct 13, 2013 at 11:14:36PM +0200, Andrew Lunn wrote:
> On Sun, Oct 13, 2013 at 11:09:15PM +0200, Andrew Lunn wrote:
> > > > I did a bisect, and the problem is in the patch:
> > > >
> > > > cpufreq: create per policy rwsem instead of per cpu cpu_policy_rwsem
> > > > e4762ba2d652dbc4c496c5abdcc80702544ca1fc
> > >
> > > Is this bug present in current linux-next?
> >
> > The current linux-next seems to be next-20130927, since Stephen
> > Rothwell is away to the moment. The patch causing the problem is not
> > in linux-next.
>
> Hi Rafael
>
> It is however in your linux-next branch:
>
> http://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/cpufreq.c?h=linux-next&id=e4762ba2d652dbc4c496c5abdcc80702544ca1fc
>
> I will build your tree and test...
Done.
It also has the bug.
Andrew
next prev parent reply other threads:[~2013-10-13 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 9:01 cpufreq-next opps with cpufreq-bench Andrew Lunn
2013-10-13 20:38 ` Rafael J. Wysocki
2013-10-13 21:09 ` Andrew Lunn
2013-10-13 21:14 ` Andrew Lunn
2013-10-13 21:45 ` Andrew Lunn [this message]
2013-10-15 23:23 ` Rafael J. Wysocki
2013-10-16 4:19 ` Viresh Kumar
2013-10-16 7:04 ` Srivatsa S. Bhat
2013-10-16 10:40 ` Rafael J. Wysocki
2013-10-17 5:04 ` Viresh Kumar
2013-10-17 14:06 ` Rafael J. Wysocki
2013-10-13 21:29 ` 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=20131013214547.GC24927@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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 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.