From: Viresh Kumar <viresh.kumar@linaro.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Kukjin Kim <kgene@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Thomas Abraham <thomas.ab@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Michael Turquette <mturquette@baylibre.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Lukasz Majewski <l.majewski@samsung.com>,
Heiko Stuebner <heiko@sntech.de>,
Chanwoo Choi <cw00.choi@samsung.com>,
Kevin Hilman <khilman@linaro.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
Anand Moon <linux.amoon@gmail.com>,
linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] cpufreq-dt: add suspend frequency support
Date: Tue, 8 Sep 2015 09:50:17 +0530 [thread overview]
Message-ID: <20150908042017.GJ26760@linux> (raw)
In-Reply-To: <55EE5C79.2030604@samsung.com>
On 08-09-15, 12:56, Krzysztof Kozlowski wrote:
> There were no comments from your side for this patchset nor for previous
> Marek's fix. After mentioned change and Bart's re-spin, do you plan to
> grab this patchset and send it for current v4.3 cycle?
Why do you think it should go via Kukjin's tree and not Rafael's?
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] cpufreq-dt: add suspend frequency support
Date: Tue, 8 Sep 2015 09:50:17 +0530 [thread overview]
Message-ID: <20150908042017.GJ26760@linux> (raw)
In-Reply-To: <55EE5C79.2030604@samsung.com>
On 08-09-15, 12:56, Krzysztof Kozlowski wrote:
> There were no comments from your side for this patchset nor for previous
> Marek's fix. After mentioned change and Bart's re-spin, do you plan to
> grab this patchset and send it for current v4.3 cycle?
Why do you think it should go via Kukjin's tree and not Rafael's?
--
viresh
next prev parent reply other threads:[~2015-09-08 4:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 15:41 [PATCH v4 0/4] cpufreq-dt: add suspend frequency support Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` [PATCH v4 1/4] PM / OPP: add dev_pm_opp_get_suspend_opp() helper Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` [PATCH v4 2/4] cpufreq: allow cpufreq_generic_suspend() to work without suspend frequency Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` [PATCH v4 3/4] cpufreq-dt: add suspend frequency support Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` Bartlomiej Zolnierkiewicz
2015-09-08 2:45 ` Viresh Kumar
2015-09-08 2:45 ` Viresh Kumar
2015-09-07 15:41 ` [PATCH v4 4/4] ARM: dts: add suspend opp to exynos4412 Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` Bartlomiej Zolnierkiewicz
2015-09-08 0:34 ` Krzysztof Kozlowski
2015-09-08 0:34 ` Krzysztof Kozlowski
2015-09-08 2:46 ` [PATCH v4 0/4] cpufreq-dt: add suspend frequency support Viresh Kumar
2015-09-08 2:46 ` Viresh Kumar
2015-09-08 3:56 ` Krzysztof Kozlowski
2015-09-08 3:56 ` Krzysztof Kozlowski
2015-09-08 4:20 ` Viresh Kumar [this message]
2015-09-08 4:20 ` Viresh Kumar
2015-09-08 4:48 ` Krzysztof Kozlowski
2015-09-08 4:48 ` Krzysztof Kozlowski
2015-09-08 5:10 ` Viresh Kumar
2015-09-08 5:10 ` Viresh Kumar
2015-09-16 22:44 ` Kukjin Kim
2015-09-16 22:44 ` Kukjin Kim
2015-09-16 22:44 ` Kukjin Kim
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=20150908042017.GJ26760@linux \
--to=viresh.kumar@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=heiko@sntech.de \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@linaro.org \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=m.szyprowski@samsung.com \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=s.nawrocki@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=tjakobi@math.uni-bielefeld.de \
--cc=tomasz.figa@gmail.com \
/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.