From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] gpio/omap: final fixes for v3.5
Date: Fri, 06 Jul 2012 16:38:22 -0700 [thread overview]
Message-ID: <87vci08npt.fsf@ti.com> (raw)
Hi Grant,
Here's a couple (hopefully) final OMAP GPIO fixes for v3.5-rc.
Thanks,
Kevin
The following changes since commit 6b16351acbd415e66ba16bf7d473ece1574cf0bc:
Linux 3.5-rc4 (2012-06-24 12:53:04 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.5/fixes/gpio-3
for you to fetch changes up to 7b86cef34afceeecf57d4d07f3cfab06f8b60b13:
gpio/omap: fix invalid context restore of gpio bank-0 (2012-07-03 09:41:39 -0700)
----------------------------------------------------------------
Grazvydas Ignotas (1):
gpio/omap: fix irq loss while in idle with debounce on
Jon Hunter (1):
gpio/omap: fix invalid context restore of gpio bank-0
drivers/gpio/gpio-omap.c | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
next reply other threads:[~2012-07-06 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 23:38 Kevin Hilman [this message]
2012-07-07 0:29 ` [GIT PULL] gpio/omap: final fixes for v3.5 Grant Likely
2012-07-09 18:07 ` Linus Walleij
2012-07-11 1:35 ` Hilman, Kevin
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=87vci08npt.fsf@ti.com \
--to=khilman@ti.com \
--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