From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
lenb@kernel.org, jean-philippe.halimi@exascale-computing.eu,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
cpufreq@vger.kernel.org
Subject: Re: [PATCH 2/2 V3] CPUFreq: Add new sysfs attribute freqdomain_cpus for acpi-freq driver
Date: Thu, 27 Jun 2013 14:13:52 +0200 [thread overview]
Message-ID: <3120815.KnnGRKg1ke@vostro.rjw.lan> (raw)
In-Reply-To: <51CBF5DC.5020806@intel.com>
On Thursday, June 27, 2013 04:20:44 PM Lan Tianyu wrote:
> On 2013年06月27日 16:25, Viresh Kumar wrote:
> > On 27 June 2013 12:38, Lan Tianyu <tianyu.lan@intel.com> wrote:
> >> Commit aa77a52 and fcf8058 changes the content of "related_cpus" and user
> >> space can't get cpus which are in the same hardware coordination cpu domain
> >> (These info are provided by ACPI AML method _PSD) via "related_cpus". This
> >> change affects some users of original "related_cpus".
> >>
> >> This patch is to add a new sysfs attribute "freqdomian_cpus" for acpi-cpufreq
> >> driver which exposes all cpus in the same domain regardless of hardware or
> >> software coordination to make up the info loss of previous change.
> >>
> >> Reference:https://bugzilla.kernel.org/show_bug.cgi?id=58761
> >> Reported-by: Jean-Philippe Halimi <jean-philippe.halimi@exascale-computing.eu>
> >> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
> >
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> >
>
> Thanks.
Queued up for 3.11 with minor changes.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-06-27 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 7:08 [PATCH 2/2 V3] CPUFreq: Add new sysfs attribute freqdomain_cpus for acpi-freq driver Lan Tianyu
2013-06-27 8:25 ` Viresh Kumar
2013-06-27 8:20 ` Lan Tianyu
2013-06-27 12:13 ` Rafael J. Wysocki [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=3120815.KnnGRKg1ke@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=jean-philippe.halimi@exascale-computing.eu \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=tianyu.lan@intel.com \
--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