All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>, Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 00/14] cpufreq: resource management in preparation for module build
Date: Wed, 4 Feb 2015 10:28:35 +0530	[thread overview]
Message-ID: <CAKohpo=3Ug9yOR2r0Dt7rr609=088ZTe1EpoYG-P-GWekFkYmQ@mail.gmail.com> (raw)
In-Reply-To: <20150203193123.GC3486@developer.amazonguestwifi.org>

On 4 February 2015 at 01:01, Eduardo Valentin <edubezval@gmail.com> wrote:
> OK. Pick what makes sense.

Because most of your patches are touching files already removed, it
requires a resend of these.

>> And please cc samsung maintainers next time ..
>
> Sure. The patches were all copied to what get_maintainers.pl told me.
> I missed them in Patch 0 though.
>
> I would appreciate if we can fix this issue so that I can send out the
> thermal changes in exynos code without breaking things apart.
>
> What would be the best way to proceed here? Would you be picking the
> rework in exynos cpufreq code and then the cleanups to make to make
> possible to build it as a module? Or should this go together with the
> thermal changes?

I think the thermal changes can go without your patches. If module removal
breaks, it would only break for exynos and nobody was using it until now
that way.

Over that, Kukjin needs to confirm what's going on with the other thread.
Why isn't that pushed to mainline yet ?

--
viresh

  reply	other threads:[~2015-02-04  4:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 20:58 [PATCH 00/14] cpufreq: resource management in preparation for module build Eduardo Valentin
2015-02-02 20:58 ` [PATCH 01/14] cpufreq: exynos4210: properly put of node Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 02/14] cpufreq: exynos4210: iounmap in error path Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 03/14] cpufreq: exynos4210: use devm_clk_get Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 04/14] cpufreq: exynos4x12: properly put of node Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 05/14] cpufreq: exynos4x12: iounmap in error path Eduardo Valentin
2015-02-02 20:58 ` [PATCH 06/14] cpufreq: exynos4x12: use devm_clk_get Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 07/14] cpufreq: exynos5250: properly put of node Eduardo Valentin
2015-02-02 20:58 ` [PATCH 08/14] cpufreq: exynos5250: iounmap in error path Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 09/14] cpufreq: exynos5250: use devm_clk_get Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 10/14] cpufreq: exynox-cpufreq: pass exynos_dvfs_info to .set_freq callback Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 11/14] cpufreq: exynos4210: remove unused symbol cpufreq Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 12/14] cpufreq: exynos4x12: " Eduardo Valentin
2015-02-02 20:58 ` [PATCH 13/14] cpufreq: exynos5250: " Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 20:58 ` [PATCH 14/14] cpufreq: exynos-cpufreq: release resources by using managed allocation Eduardo Valentin
2015-02-02 20:58   ` Eduardo Valentin
2015-02-02 22:54 ` [PATCH 00/14] cpufreq: resource management in preparation for module build Rafael J. Wysocki
2015-02-03  4:05 ` Viresh Kumar
2015-02-03 19:31   ` Eduardo Valentin
2015-02-04  4:58     ` Viresh Kumar [this message]
2015-02-04  8:52 ` Lukasz Majewski
2015-02-04  9:56   ` Viresh Kumar

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='CAKohpo=3Ug9yOR2r0Dt7rr609=088ZTe1EpoYG-P-GWekFkYmQ@mail.gmail.com' \
    --to=viresh.kumar@linaro.org \
    --cc=edubezval@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-pm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.