From: amit.daniel@samsung.com (Amit Daniel Kachhap)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 2/4] cpufreq: exynos: Remove error return even if no soc is found
Date: Thu, 28 Mar 2013 13:35:20 +0530 [thread overview]
Message-ID: <1364457923-8499-3-git-send-email-amit.daniel@samsung.com> (raw)
In-Reply-To: <1364457923-8499-1-git-send-email-amit.daniel@samsung.com>
This patch helps to have single binary for exynos5440 and previous
exynos soc's. This change is needed for adding exynos5440 cpufreq driver
which does not uses exynos-cpufreq common file and adds it own driver.
Signed-off-by: Amit Daniel Kachhap <amit.daniel@samsung.com>
---
drivers/cpufreq/exynos-cpufreq.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c
index 78057a3..ee75997 100644
--- a/drivers/cpufreq/exynos-cpufreq.c
+++ b/drivers/cpufreq/exynos-cpufreq.c
@@ -297,7 +297,7 @@ static int __init exynos_cpufreq_init(void)
else if (soc_is_exynos5250())
ret = exynos5250_cpufreq_init(exynos_info);
else
- pr_err("%s: CPU type not found\n", __func__);
+ return 0;
if (ret)
goto err_vdd_arm;
--
1.7.1
next prev parent reply other threads:[~2013-03-28 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 8:05 [PATCH V5 0/4] cpufreq: exynos5440: support for cpufreq driver Amit Daniel Kachhap
2013-03-28 8:05 ` [PATCH V5 1/4] cpufreq: exynos: Add cpufreq driver for exynos5440 Amit Daniel Kachhap
2013-03-28 8:53 ` Viresh Kumar
2013-03-28 12:42 ` Viresh Kumar
2013-04-08 8:25 ` amit daniel kachhap
2013-03-28 8:05 ` Amit Daniel Kachhap [this message]
2013-03-28 8:05 ` [PATCH V5 3/4] arm: exynos: Enable OPP library support " Amit Daniel Kachhap
2013-03-28 8:05 ` [PATCH V5 4/4] arm: dts: Add cpufreq controller node for Exynos5440 SoC Amit Daniel Kachhap
2013-03-28 8:33 ` [PATCH V5 0/4] cpufreq: exynos5440: support for cpufreq driver Viresh Kumar
2013-04-05 12:38 ` Rafael J. Wysocki
2013-04-08 8:36 ` amit daniel kachhap
2013-04-08 12:02 ` Kukjin Kim
2013-04-08 19:49 ` Rafael J. Wysocki
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=1364457923-8499-3-git-send-email-amit.daniel@samsung.com \
--to=amit.daniel@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;
as well as URLs for NNTP newsgroup(s).