linux-kernel - Re: [PATCH] cpufreq: acpi: Add comment under ACPI_ADR_SPACE_SYSTEM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4207904.oBhTxYOkzS@vostro.rjw.lan>
Date:	Tue, 22 Oct 2013 00:39:45 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	Patch Tracking <patches@...aro.org>,
	"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cpufreq: acpi: Add comment under ACPI_ADR_SPACE_SYSTEM_IO case

On Monday, October 21, 2013 12:43:32 PM Viresh Kumar wrote:
> On 13 October 2013 06:07, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> > On 13/10/2013, Rafael J. Wysocki <rjw@...k.pl> wrote:
> >> -> What about this:
> >>
> >>       /*
> >>        * The core will not set policy->cur, because cpufreq_driver->get is NULL,
> >>        * so we need to set it here.  However, we have to guess it, because the
> >>        * current speed is unknown and not detectable via IO ports.
> >>        */
> >
> > Far better. Attached again. Thanks.
> 
> Have you missed applying this one? Attached again..

I don't think I've missed it.  It should be commit 1bab64d in my tree.

Thanks!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/