From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: create link to policy only for registered CPUs
Date: Fri, 9 Sep 2016 12:28:41 +0100 [thread overview]
Message-ID: <20160909112841.GS1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20160909112204.GE18547@vireshk-i7>
On Fri, Sep 09, 2016 at 04:52:04PM +0530, Viresh Kumar wrote:
> Thanks for testing it.. You need another patch from Rafael, which
> should be in linux-next by now..
>
> commit 3689ad7ed6a8 ("cpufreq: Drop unnecessary check from
> cpufreq_policy_alloc()")
>
> Both patches combined will fix the problem you were getting.
Please send me this other patch. Seems absurd to fix a reported problem
without copying appropriate patches to the reporter...
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-09-09 11:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 11:00 Kernel warning in cpufreq_add_dev() Russell King - ARM Linux
2016-08-20 1:29 ` Rafael J. Wysocki
2016-08-20 1:46 ` Viresh Kumar
2016-08-22 17:32 ` Rafael J. Wysocki
2016-08-24 13:13 ` Viresh Kumar
2016-08-31 1:26 ` Rafael J. Wysocki
2016-08-31 4:11 ` Viresh Kumar
2016-08-31 11:58 ` Rafael J. Wysocki
2016-09-09 9:57 ` Viresh Kumar
2016-09-09 9:54 ` [PATCH] cpufreq: create link to policy only for registered CPUs Viresh Kumar
2016-09-09 11:16 ` Russell King - ARM Linux
2016-09-09 11:22 ` Viresh Kumar
2016-09-09 11:28 ` Russell King - ARM Linux [this message]
2016-09-09 11:34 ` Viresh Kumar
2016-09-09 12:53 ` Russell King - ARM Linux
2016-09-12 6:37 ` [PATCH V2] " Viresh Kumar
2016-09-14 1:00 ` 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=20160909112841.GS1041@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).