From: Magnus Damm <magnus.damm@gmail.com>
To: linux-input@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>,
lethal@linux-sh.org, akpm@linux-foundation.org,
linux-sh@vger.kernel.org
Subject: [PATCH 00/03] sh: SuperH KEYSC keypad support
Date: Fri, 29 Feb 2008 19:48:47 +0900 [thread overview]
Message-ID: <20080229104847.22537.66432.sendpatchset@clockwork.opensource.se> (raw)
These patches add support for keypads attached to the SuperH KEYSC block.
[PATCH 01/03] sh: SuperH KEYSC platform driver
[PATCH 02/03] sh: SuperH KEYSC support for MigoR
[PATCH 03/03] sh: SuperH KEYSC support for Solution Engine 7722
Signed-off-by: Magnus Damm <damm@igel.co.jp>
---
Please note that the board patches need the header file provided by
the first patch to compile. So maybe this is suitable for -mm?
If it is better to merge the driver in some subsystem tree then I'll
just resend the board code to the linux-sh list during late -rc1 merge.
arch/sh/boards/renesas/migor/setup.c | 56 ++++++
arch/sh/boards/se/7722/setup.c | 41 ++++
drivers/input/keyboard/Kconfig | 9 +
drivers/input/keyboard/Makefile | 1
drivers/input/keyboard/sh_keysc.c | 281 ++++++++++++++++++++++++++++++++++
include/asm-sh/se7722.h | 2
include/asm-sh/sh_keysc.h | 13 +
7 files changed, 402 insertions(+), 1 deletion(-)
next reply other threads:[~2008-02-29 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 10:48 Magnus Damm [this message]
2008-02-29 10:48 ` [PATCH 01/03] sh: SuperH KEYSC platform driver Magnus Damm
2008-02-29 21:57 ` Andrew Morton
2008-02-29 10:49 ` [PATCH 02/03] sh: SuperH KEYSC keypad data for MigoR Magnus Damm
2008-02-29 10:49 ` [PATCH 03/03] sh: SuperH KEYSC keypad data for Solution Engine 7722 Magnus Damm
2008-02-29 22:01 ` [PATCH 00/03] sh: SuperH KEYSC keypad support Andrew Morton
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=20080229104847.22537.66432.sendpatchset@clockwork.opensource.se \
--to=magnus.damm@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-input@vger.kernel.org \
--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 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).