All of lore.kernel.org
 help / color / mirror / Atom feed
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 22:25:03 +0530	[thread overview]
Message-ID: <CAKohpo=6PDxFvmwQvb2V3Qpq2ZVtxQo-8kLwqnJpvwOjtUa7yA@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUWo4um9s-FhF5HoN5-WbkbNDTjnGkMMRHc60GWohcrPvA@mail.gmail.com>

On 8 February 2013 22:21, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> No, it did NOT apply cleanly and I merged your tree like this.

Patch looks fine to me.

>> To me it does not look like your changes from the patch you sent me
>> are included?

Yes they do. Check most of the changes from cpufreq.c which remove
locks around init/exit.

> Looks like I did it correct - no WARNINGs.
>
> So, suspend-resume is good here.

Great!!

      reply	other threads:[~2013-02-08 16:55 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
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 [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='CAKohpo=6PDxFvmwQvb2V3Qpq2ZVtxQo-8kLwqnJpvwOjtUa7yA@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.