linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	skannan@codeaurora.org, shilpa.bhat@linux.vnet.ibm.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "cpufreq: postfix policy directory with the first CPU in related_cpus"
Date: Wed, 9 Mar 2016 16:39:27 +0700	[thread overview]
Message-ID: <20160309093927.GI23015@vireshk-mac-ubuntu> (raw)
In-Reply-To: <eb862848df536cb2921945cca690161014c84750.1456996795.git.viresh.kumar@linaro.org>

On 03-03-16, 14:51, Viresh Kumar wrote:
> This reverts commit 3510fac45492 ("cpufreq: postfix policy directory
> with the first CPU in related_cpus").
> 
> Earlier, the policy->kobj was added to the kobject core, before ->init()
> callback was called for the cpufreq drivers. Which allowed those drivers
> to add or remove, driver dependent, sysfs files/directories to the same
> kobj from their ->init() and ->exit() callbacks.
> 
> That isn't possible anymore after commit 3510fac45492 got applied.
> 
> Now, there is no other clean alternative that people can adopt.
> 
> Its better to revert the earlier commit to allow cpufreq drivers to
> create/remove sysfs files from ->init() and ->exit() callbacks.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

Sorry about missing SoB (Just noticed it in bleeding-edge).
-- 
viresh

  reply	other threads:[~2016-03-09  9:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03  9:21 [PATCH] Revert "cpufreq: postfix policy directory with the first CPU in related_cpus" Viresh Kumar
2016-03-09  9:39 ` Viresh Kumar [this message]
2016-03-09 13:12   ` 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=20160309093927.GI23015@vireshk-mac-ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=shilpa.bhat@linux.vnet.ibm.com \
    --cc=skannan@codeaurora.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).