From: David Brownell <david-b@pacbell.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>,
"Russell King" <rmk@arm.linux.org.uk>,
lkml <linux-kernel@vger.kernel.org>
Subject: [patch 2.6.26-rc3] gpio: build fixes (mostly potential)
Date: Mon, 19 May 2008 15:50:18 -0700 [thread overview]
Message-ID: <200805191550.18937.david-b@pacbell.net> (raw)
This fixes various gpio-related build errors (mostly potential)
reported by Russell King and Uwe Kleine-König.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
---
include/asm-generic/gpio.h | 4 +++-
include/linux/gpio.h | 2 ++
2 files changed, 5 insertions(+), 1 deletion(-)
--- a/include/asm-generic/gpio.h 2008-05-19 14:59:51.000000000 -0700
+++ b/include/asm-generic/gpio.h 2008-05-19 15:05:18.000000000 -0700
@@ -3,6 +3,8 @@
#ifdef CONFIG_HAVE_GPIO_LIB
+#include <linux/compiler.h>
+
/* Platforms may implement their GPIO interface with library code,
* at a small performance cost for non-inlined operations and some
* extra memory (for code and for per-GPIO table entries).
@@ -74,7 +76,7 @@ struct gpio_chip {
extern const char *gpiochip_is_requested(struct gpio_chip *chip,
unsigned offset);
-extern int __init __must_check gpiochip_reserve(int start, int ngpio);
+extern int __must_check gpiochip_reserve(int start, int ngpio);
/* add/remove chips */
extern int gpiochip_add(struct gpio_chip *chip);
--- a/include/linux/gpio.h 2008-05-19 15:05:34.000000000 -0700
+++ b/include/linux/gpio.h 2008-05-19 15:06:54.000000000 -0700
@@ -8,6 +8,8 @@
#else
+#include <linux/errno.h>
+
/*
* Some platforms don't support the GPIO programming interface.
*
next reply other threads:[~2008-05-20 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 22:50 David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-20 23:17 [patch 2.6.26-rc3] gpio: build fixes (mostly potential) David Brownell
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=200805191550.18937.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=Uwe.Kleine-Koenig@digi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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