From: Ben Dooks <ben@simtec.co.uk>
To: linux-input@vger.kernel.org
Cc: Simtec Linux Team <linux@simtec.co.uk>
Subject: [patch 2/3] gpio_keys: use <linux/gpio.h> instead of <asm/gpio.h>
Date: Tue, 10 Nov 2009 22:59:39 +0000 [thread overview]
Message-ID: <20091110230002.668609324@fluff.org.uk> (raw)
In-Reply-To: 20091110225937.922379610@fluff.org.uk
[-- Attachment #1: simtec/ready/gpio-buttons-fix-include.patch --]
[-- Type: text/plain, Size: 761 bytes --]
The gpio keys driver should be using <linux/gpio.h> instead of <asm/gpio.h>
Signed-off-by: Ben Dooks <ben@simtec.co.uk>
Signed-off-by: Simtec Linux Team <linux@simtec.co.uk>
---
drivers/input/keyboard/gpio_keys.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Index: b/drivers/input/keyboard/gpio_keys.c
===================================================================
--- a/drivers/input/keyboard/gpio_keys.c 2009-11-02 21:45:30.000000000 +0000
+++ b/drivers/input/keyboard/gpio_keys.c 2009-11-02 22:03:01.000000000 +0000
@@ -23,8 +23,7 @@
#include <linux/input.h>
#include <linux/gpio_keys.h>
#include <linux/workqueue.h>
-
-#include <asm/gpio.h>
+#include <linux/gpio.h>
struct gpio_button_data {
struct gpio_keys_button *button;
next prev parent reply other threads:[~2009-11-10 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 22:59 [patch 0/3] gpio_keys driver updates Ben Dooks
2009-11-10 22:59 ` [patch 1/3] gpio_keys: use dev_ macros to report information Ben Dooks
2009-11-10 22:59 ` Ben Dooks [this message]
2009-11-10 22:59 ` [patch 3/3] gpio_keys: seperate individual button setup to make code neater Ben Dooks
2009-11-11 5:08 ` [patch 0/3] gpio_keys driver updates Dmitry Torokhov
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=20091110230002.668609324@fluff.org.uk \
--to=ben@simtec.co.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux@simtec.co.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 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.