From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: "Kukjin Kim" <kgene@kernel.org>, 최찬우 <cw00.choi@samsung.com>
Cc: 박경민 <kyungmin.park@samsung.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"ABHILASH KESAVAN" <a.kesavan@samsung.com>,
"tomasz.figa@gmail.com" <tomasz.figa@gmail.com>,
"Krzysztof Kozlowski" <k.kozlowski@samsung.com>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
대인기 <inki.dae@samsung.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Subject: Re: RE: [PATCH v9 0/7] devfreq: Add devfreq-event class to provide raw data for devfreq device
Date: Mon, 26 Jan 2015 02:06:54 +0000 (GMT) [thread overview]
Message-ID: <298834569.29261422238011182.JavaMail.weblogic@epmlwas04d> (raw)
>
> Chanwoo Choi wrote:
> >
> Hi,
>
[]
> >
> > --
>
> Looks good to me.
>
> Myungjoo, shall I take DT changes in this series into Samsung tree?
>
> 4/7 ARM: dts: Add PPMU dt node for Exynos3250 SoC
> 5/7 ARM: dts: Add PPMU dt node for Exynos4 SoCs
> 6/7 ARM: dts: exynos: Add PPMU node for Exynos3250-based Rinato/Monk board
> 7/7 ARM: dts: exynos: Add PPMU node for Exynos4412-based TRATS2 board
Yes, you may take those. I am not so confident with taking DT patches, either.
However, Chanwoo has another updates following for this patchset.
After that, I guess we can merge chanwoo's patchset splitted.
Cheers,
MyungJoo.
>
> Thanks,
> Kukjin
>
next reply other threads:[~2015-01-26 2:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 2:06 MyungJoo Ham [this message]
2015-01-26 2:11 ` [PATCH v9 0/7] devfreq: Add devfreq-event class to provide raw data for devfreq device Chanwoo Choi
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=298834569.29261422238011182.JavaMail.weblogic@epmlwas04d \
--to=myungjoo.ham@samsung.com \
--cc=a.kesavan@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=inki.dae@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--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 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).