From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: Fwd: [PATCH v2 0/8] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3
Date: Mon, 02 May 2016 08:06:13 +0200 [thread overview]
Message-ID: <5726EE55.7050204@samsung.com> (raw)
In-Reply-To: <5726EBD7.30403@samsung.com>
On 05/02/2016 07:55 AM, Krzysztof Kozlowski wrote:
> On 05/02/2016 07:48 AM, MyungJoo Ham wrote:
>> Sender : ???<cw00.choi@samsung.com> S5(??)/Change Agent/Tizen Platform Lab(S/W??)/????
>> Date : 2016-04-15 15:32 (GMT+09:00)
>>>
>>> This patchset support the AMBA bus frequency scaling on Exynos5422-based
>>> Odroid-XU3 board. But, this series only support the bus frequency scaling
>>> for INT (Internal) block using VDD_INT power line.
>>
>> Along with Devfreq/Passive patchset, the patchset is merged in
>> devfreq for-4.7 tree.
>>
>> https://git.kernel.org/cgit/linux/kernel/git/mzx/devfreq.git/log/?h=for-4.7
>>
>> @Chanwoo: If there are commits to be merged by a tree other than Linux/PM,
>> please let me know. I'll send out pull-request soon.
>
> As we discussed before, don't apply the DTS changes. The DTS are
> independent so they should go through samsung/arm-soc.
Another point is that you applied patches without your signed-off-by...
that is not the proper way. If you touch a patch or apply it, you must
signed it off.
BR,
Krzysztof
next prev parent reply other threads:[~2016-05-02 6:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 5:48 Fwd: [PATCH v2 0/8] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3 MyungJoo Ham
2016-05-02 5:55 ` Krzysztof Kozlowski
2016-05-02 6:06 ` Krzysztof Kozlowski [this message]
2016-05-02 6:24 ` Krzysztof Kozlowski
2016-05-03 2:17 ` 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=5726EE55.7050204@samsung.com \
--to=k.kozlowski@samsung.com \
--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