From: Viresh Kumar <viresh.kumar@linaro.org>
To: sedat.dilek@gmail.com
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Stephen Rothwell <sfr@canb.auug.org.au>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Linux ACPI <linux-acpi@vger.kernel.org>,
Hillf Danton <dhillf@gmail.com>,
linux-next@vger.kernel.org,
Linux PM List <linux-pm@lists.linux-foundation.org>,
Chuansheng Liu <chuansheng.liu@intel.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [linux-pm] linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
Date: Fri, 8 Feb 2013 20:26:16 +0530 [thread overview]
Message-ID: <CAOh2x=nn24DC-jpD_UsZ2z6=5d9GmZqwowKF8X0zQQX=vZmbqQ@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUUedcLAo1OkDSD7K_zgZoLvUAPNYOWAJxSPLp9J3hCKNw@mail.gmail.com>
On Fri, Feb 8, 2013 at 8:18 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> Nah, I pulled in latest pm-next where this commit is new...
>
> commit 8d5666f3456f2fd4a4e5dced228475b829851e53
> "ACPI: Unbind ACPI drv when probe failed"
>
> ...building with it.
>
> Same to you, say concretely which commit is fixing what...
>
> Pull-N-B-Happy was never my strategy... I want to understand what went
> wrong and have stolen my time.
I don't have any pointers to broken tree and so can't point you to the culprit,
but it was this patch:
http://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=commit;h=e034e731f4d9d18ad0401f033f485a3096796c58
minus
the patch i sent you as attachment.
There were some locking introduced around init/exit of cpufreq_driver, which
caused some drivers to break. Its fixed now in the above commit.
next prev parent reply other threads:[~2013-02-08 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 8:46 linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ] Sedat Dilek
2013-02-08 11:53 ` Hillf Danton
2013-02-08 12:47 ` Sedat Dilek
2013-02-08 13:21 ` Rafael J. Wysocki
2013-02-08 13:58 ` Ingo Molnar
2013-02-08 14:15 ` Sedat Dilek
2013-02-08 14:50 ` Viresh Kumar
2013-02-08 15:19 ` Sedat Dilek
2013-02-08 14:45 ` [linux-pm] " Viresh Kumar
2013-02-08 14:48 ` Sedat Dilek
2013-02-08 14:56 ` Viresh Kumar [this message]
2013-02-08 15:21 ` Sedat Dilek
2013-02-08 16:28 ` Sedat Dilek
2013-02-08 16:51 ` Sedat Dilek
2013-02-08 16:55 ` 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='CAOh2x=nn24DC-jpD_UsZ2z6=5d9GmZqwowKF8X0zQQX=vZmbqQ@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=chuansheng.liu@intel.com \
--cc=dhillf@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@redhat.com \
--cc=rjw@sisk.pl \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=x86@kernel.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.