From: Simon Horman <horms+renesas@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: shmobile: lager, koelsch: set .debounce_interval
Date: Tue, 29 Oct 2013 08:57:29 +0000 [thread overview]
Message-ID: <1383037051-21427-1-git-send-email-horms+renesas@verge.net.au> (raw)
This short series sets .debounce_interval for GPIO keys
for the lager and koelsch boards.
This resolves a problem on the lager board reported, tested and fixed by
Kuribayashi-san. I have extended the solution to the koelsch board.
Shinya Kuribayashi (1):
ARM: shmobile: lager: set .debounce_interval
Simon Horman (1):
ARM: shmobile: koelsch: set .debounce_interval
arch/arm/mach-shmobile/board-koelsch.c | 3 ++-
arch/arm/mach-shmobile/board-lager.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
--
1.8.4
next reply other threads:[~2013-10-29 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 8:57 Simon Horman [this message]
2013-10-29 8:57 ` [PATCH 1/2] ARM: shmobile: lager: set .debounce_interval Simon Horman
2013-10-29 8:57 ` [PATCH 2/2] ARM: shmobile: koelsch: " Simon Horman
2013-10-31 5:13 ` [PATCH 0/2] ARM: shmobile: lager, " Simon Horman
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=1383037051-21427-1-git-send-email-horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).