public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: kgene.kim@samsung•com (Kukjin Kim)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 06/11] PM / devfreq: move definitions for exynos4_bus into drivers/devfreq
Date: Thu, 19 Dec 2013 02:54:30 +0900	[thread overview]
Message-ID: <52B1E156.6030904@samsung.com> (raw)
In-Reply-To: <CAJ0PZbTH0kga7Gbb87umJpCF_ih3TQrxKS0xBbofDvJq+_wj5Q@mail.gmail.com>

On 12/18/13 15:11, MyungJoo Ham wrote:
> On Tue, Dec 17, 2013 at 8:52 PM,<kgene@kernel•org>  wrote:
>> From: Kukjin Kim<kgene.kim@samsung•com>
>>
>> We don't need to keep the definitions for exynos4_bus into
>> mach-exynos/ so this moves them into drviers/devfreq with
>> adding header file.
>
> Acked-by: MyungJoo Ham<myungjoo.ham@samsung•com>
>
> However, how are you going to merge this patch?
> Do you need me to get this handled or are you going to do it yourself
> with Samsung-SoC tree?
>

Hi MyungJoo,

Let me take this into Samsung tree with others if you're OK :-)

Thanks,
Kukjin

> Cheers,
> MyungJoo.
>
>>
>> Cc: MyungJoo Ham<myungjoo.ham@samsung•com>
>> Signed-off-by: Kukjin Kim<kgene.kim@samsung•com>
>> ---
>>   arch/arm/mach-exynos/include/mach/regs-clock.h |   94 --------------------
>>   drivers/devfreq/exynos/exynos4_bus.c           |    4 +-
>>   drivers/devfreq/exynos/exynos4_bus.h           |  110
>> ++++++++++++++++++++++++
>>   3 files changed, 112 insertions(+), 96 deletions(-)
>>   create mode 100644 drivers/devfreq/exynos/exynos4_bus.h

  reply	other threads:[~2013-12-18 17:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 11:52 [PATCH 06/11] PM / devfreq: move definitions for exynos4_bus into drivers/devfreq kgene at kernel.org
2013-12-18  6:11 ` MyungJoo Ham
2013-12-18 17:54   ` Kukjin Kim [this message]
2013-12-19  7:29     ` MyungJoo Ham

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=52B1E156.6030904@samsung.com \
    --to=kgene.kim@samsung$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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