From: Abhilash Kesavan <a.kesavan@samsung.com>
To: myungjoo.ham@samsung.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, kgene.kim@samsung.com
Cc: kyungmin.park@samsung.com, rjw@sisk.pl, jhbird.choi@samsung.com
Subject: [PATCH v4 3/4] PM: DEVFREQ: Move exynos4 devfreq driver into a new sub-directory
Date: Fri, 18 Jan 2013 18:54:29 +0530 [thread overview]
Message-ID: <1358515469-7529-1-git-send-email-a.kesavan@samsung.com> (raw)
In-Reply-To: <1357733199-17206-3-git-send-email-a.kesavan@samsung.com>
In anticipation of the new exynos5 devfreq and ppmu driver, create
an exynos sub-directory. Move the existing exynos4 devfreq driver
into the same.
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Jonghwan Choi <jhbird.choi@samsung.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>
---
Note: No changes, rebased against latest tree. Only compile
tested for Exynos4.
drivers/devfreq/Makefile | 2 +-
drivers/devfreq/exynos/Makefile | 2 ++
drivers/devfreq/{ => exynos}/exynos4_bus.c | 0
3 files changed, 3 insertions(+), 1 deletions(-)
create mode 100644 drivers/devfreq/exynos/Makefile
rename drivers/devfreq/{ => exynos}/exynos4_bus.c (100%)
diff --git a/drivers/devfreq/Makefile b/drivers/devfreq/Makefile
index 8c46423..3bc1fef 100644
--- a/drivers/devfreq/Makefile
+++ b/drivers/devfreq/Makefile
@@ -5,4 +5,4 @@ obj-$(CONFIG_DEVFREQ_GOV_POWERSAVE) += governor_powersave.o
obj-$(CONFIG_DEVFREQ_GOV_USERSPACE) += governor_userspace.o
# DEVFREQ Drivers
-obj-$(CONFIG_ARM_EXYNOS4_BUS_DEVFREQ) += exynos4_bus.o
+obj-$(CONFIG_ARM_EXYNOS4_BUS_DEVFREQ) += exynos/
diff --git a/drivers/devfreq/exynos/Makefile b/drivers/devfreq/exynos/Makefile
new file mode 100644
index 0000000..1498823
--- /dev/null
+++ b/drivers/devfreq/exynos/Makefile
@@ -0,0 +1,2 @@
+# Exynos DEVFREQ Drivers
+obj-$(CONFIG_ARM_EXYNOS4_BUS_DEVFREQ) += exynos4_bus.o
diff --git a/drivers/devfreq/exynos4_bus.c b/drivers/devfreq/exynos/exynos4_bus.c
similarity index 100%
rename from drivers/devfreq/exynos4_bus.c
rename to drivers/devfreq/exynos/exynos4_bus.c
--
1.7.8.6
next prev parent reply other threads:[~2013-01-18 13:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 12:06 [PATCH 1/4] ARM: EXYNOS5: Add PPMU device tree support Abhilash Kesavan
2013-01-09 12:06 ` [PATCH 2/4] ARM: EXYNOS5: Support Exynos5-bus devfreq driver Abhilash Kesavan
2013-01-14 14:29 ` MyungJoo Ham
2013-01-18 13:23 ` [PATCH v4 " Abhilash Kesavan
2013-01-09 12:06 ` [PATCH 3/4] PM: DEVFREQ: Move exynos4 devfreq driver into a new sub-directory Abhilash Kesavan
2013-01-14 14:30 ` MyungJoo Ham
2013-01-18 13:24 ` Abhilash Kesavan [this message]
2013-01-09 12:06 ` [PATCH 4/4] PM/Devfreq: Add Exynos5-bus devfreq driver for Exynos5250 Abhilash Kesavan
2013-01-09 14:14 ` Rajagopal Venkat
2013-01-18 13:22 ` Abhilash Kesavan
2013-01-18 13:24 ` [PATCH v4 4/4] PM: Devfreq: " Abhilash Kesavan
2013-02-03 15:47 ` Abhilash Kesavan
2013-02-04 6:41 ` myungjoo.ham
2013-02-04 8:03 ` Abhilash Kesavan
2013-02-04 12:14 ` [PATCH v5 " Abhilash Kesavan
2013-02-05 9:56 ` MyungJoo Ham
2013-01-14 14:26 ` [PATCH 1/4] ARM: EXYNOS5: Add PPMU device tree support MyungJoo Ham
2013-01-18 13:23 ` [PATCH v4 " Abhilash Kesavan
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=1358515469-7529-1-git-send-email-a.kesavan@samsung.com \
--to=a.kesavan@samsung.com \
--cc=jhbird.choi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®