linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Rafael Wysocki <rafael.j.wysocki@intel.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] crash on reading cpufreq sysfs
Date: Thu, 08 Oct 2015 08:17:57 -0700	[thread overview]
Message-ID: <1444317477.2971.1.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0j0=WKGoERT_uJjs=gkAiDuR2_RdTOTObHx9up-vzLZuQ@mail.gmail.com>

On Thu, 2015-10-08 at 02:17 +0200, Rafael J. Wysocki wrote:
> On Thu, Oct 8, 2015 at 1:50 AM, Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> > On Thu, 2015-10-08 at 00:50 +0200, Rafael J. Wysocki wrote:
> > > On Wednesday, October 07, 2015 01:50:42 PM Srinivas Pandruvada
> > > wrote:
> > > > Fixes for crash on reading cpufreq sysfs for offline cpus
> > > > 
> > > > v1
> > > > Fix commit discription on Patch 1/2. Included Acks from Viresh.
> > > > It has both patches, even though only one patch has change.
> > > > 
> > > > v0
> > > > two patches: one for acp-cpufreq and one for cpufreq core
> > > > 
> > > > Srinivas Pandruvada (2):
> > > >   cpufreq: acpi_cpufreq: prevent crash on reading
> > > > freqdomain_cpus
> > > >   cpufreq: prevent lockup on reading
> > > > scaling_available_frequencies
> > > 
> > > Both applied, but they look like -stable material to me.
> > > 
> > I tested in 4.1 kernels, since on offline, cpufreq folder is not
> > available there is no issue.
> > For 4.2 kernels the I didn't see crash fixed by cpufreq core patch
> > (cat
> > scaling_available_frequencies), but the "cat freqdomain_cpus" still
> > causes crash. So we need to apply cpufreq:acpi-cpufreq patch only.
> > So
> > one patch is applicable for stable tree.
> 
> So [1/2] should go into 4.2.y and [2/2] fixes a regression introduced
> in this cycle, right?
Yes.

Thanks,
Srinivas
> 
> Thanks,
> Rafael

  reply	other threads:[~2015-10-08 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 20:50 [PATCH v1 0/2] crash on reading cpufreq sysfs Srinivas Pandruvada
2015-10-07 20:50 ` [PATCH v1 1/2] cpufreq: acpi_cpufreq: prevent crash on reading freqdomain_cpus Srinivas Pandruvada
2015-10-07 20:50 ` [PATCH v1 2/2] cpufreq: prevent lockup on reading scaling_available_frequencies Srinivas Pandruvada
2015-10-07 22:50 ` [PATCH v1 0/2] crash on reading cpufreq sysfs Rafael J. Wysocki
2015-10-07 23:50   ` Srinivas Pandruvada
2015-10-08  0:17     ` Rafael J. Wysocki
2015-10-08 15:17       ` Srinivas Pandruvada [this message]
2015-10-08 20:19         ` 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=1444317477.2971.1.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@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 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).