From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>, arnd.bergmann@linaro.org
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
kgene.kim@samsung.com, xf@rock-chips.com, heiko@sntech.de,
mmcclint@codeaurora.org, k.kozlowski@samsung.com,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH V3 1/4] cpufreq: dt: Include types.h from cpufreq-dt.h
Date: Wed, 30 Mar 2016 13:45:25 +0530 [thread overview]
Message-ID: <761afb1626b6e044bbddca711ba74900991b725f.1459325515.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1459325515.git.viresh.kumar@linaro.org>
In-Reply-To: <cover.1459325515.git.viresh.kumar@linaro.org>
cpufreq-dt.h uses 'bool' data type but doesn't include types.h. It works
fine for now as the files that include cpufreq-dt.h, also include
types.h directly or indirectly.
But, when a file includes cpufreq-dt.h without including types.h, we get
a build error. Avoid such errors by including types.h in cpufreq-dt
itself.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
include/linux/cpufreq-dt.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/cpufreq-dt.h b/include/linux/cpufreq-dt.h
index 0414009e2c30..a87335a1660c 100644
--- a/include/linux/cpufreq-dt.h
+++ b/include/linux/cpufreq-dt.h
@@ -10,6 +10,8 @@
#ifndef __CPUFREQ_DT_H__
#define __CPUFREQ_DT_H__
+#include <linux/types.h>
+
struct cpufreq_dt_platform_data {
/*
* True when each CPU has its own clock to control its
--
2.7.1.410.g6faf27b
next prev parent reply other threads:[~2016-03-30 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 8:15 [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-03-30 8:15 ` Viresh Kumar [this message]
2016-03-30 8:15 ` [PATCH V3 2/4] cpufreq: dt: Add generic platform-device creation support Viresh Kumar
2016-04-13 19:46 ` Matthew McClintock
2016-03-30 8:15 ` [PATCH V3 3/4] ARM: exynos: exynos-cpufreq platform device isn't supported anymore Viresh Kumar
2016-03-30 8:30 ` Krzysztof Kozlowski
2016-03-30 8:15 ` [PATCH V3 4/4] cpufreq: exynos: Use generic platdev driver Viresh Kumar
2016-04-07 8:31 ` [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-04-20 9:55 ` Viresh Kumar
2016-04-20 21:27 ` Mason
2016-04-20 22:31 ` Rafael J. Wysocki
2016-04-27 16:47 ` Mason
2016-04-27 16:57 ` Matthew McClintock
2016-04-28 2:27 ` Viresh Kumar
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=761afb1626b6e044bbddca711ba74900991b725f.1459325515.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=heiko@sntech.de \
--cc=k.kozlowski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmcclint@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=xf@rock-chips.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).