From: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
To: linux-sh@vger.kernel.org
Subject: [PATCH 3.4.0-rc3] sh:pfc: include sh_pfc.h header file.
Date: Thu, 19 Apr 2012 10:06:30 +0000 [thread overview]
Message-ID: <1334829990-9196-1-git-send-email-srinivas.kandagatla@st.com> (raw)
This patch includes sh_pfc.h in pfc.c file, without this include kernel
build with CONFIG_GENERIC_GPIO will throw below errors.
drivers/sh/pfc.c:25:32: warning: ‘struct pinmux_info’ declared inside
parameter list [enabled by default]
drivers/sh/pfc.c:25:32: warning: its scope is only this definition or
declaration, which is probably not what you want [enabled by default]
drivers/sh/pfc.c: In function ‘pfc_iounmap’:
drivers/sh/pfc.c:29:21: error: dereferencing pointer to incomplete type
drivers/sh/pfc.c:30:10:error: dereferencing pointer to incomplete type
drivers/sh/pfc.c:31:15:error: dereferencing pointer to incomplete type
drivers/sh/pfc.c:33:11: error: dereferencing pointer to incomplete type
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@st.com>
---
Hi All,
This patch fixes a compilation error in the sh kernel build if CONFIG_GENERIC_GPIO is enabled.
--srini
drivers/sh/pfc.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/sh/pfc.c b/drivers/sh/pfc.c
index 522c6c4..505d7cf 100644
--- a/drivers/sh/pfc.c
+++ b/drivers/sh/pfc.c
@@ -21,6 +21,7 @@
#include <linux/gpio.h>
#include <linux/slab.h>
#include <linux/ioport.h>
+#include <linux/sh_pfc.h>
static void pfc_iounmap(struct pinmux_info *pip)
{
--
1.7.0.4
next reply other threads:[~2012-04-19 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 10:06 Srinivas KANDAGATLA [this message]
2012-04-19 10:23 ` [PATCH 3.4.0-rc3] sh:pfc: include sh_pfc.h header file Srinivas KANDAGATLA
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=1334829990-9196-1-git-send-email-srinivas.kandagatla@st.com \
--to=srinivas.kandagatla@st.com \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.