From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Byron Bradley <byron.bbradley@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
akpm@linux-foundation.org, nico@cam.org, buytenh@wantstofly.org
Subject: Re: 2.6.26-rc2-mm1: oops on ARM while registering GPIO Keys
Date: Wed, 14 May 2008 11:52:18 -0400 [thread overview]
Message-ID: <20080514115114.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0805141620080.3865@gamma>
On Wed, May 14, 2008 at 04:34:41PM +0100, Byron Bradley wrote:
> Testing on a QNAP TS-209 (ARM, Marvell Orion 88F5182 SoC). GPIO Keys works
> correctly on 2.6.26-rc2 but panics on 2.6.26-rc2-mm1. If nobody knows the
> cause of this I can look into it/bisect later.
>
Yeah, it seems I applied the wrong version of the debouncing patch.
Just revert git-input from -mm for now.
--
Dmitry
prev parent reply other threads:[~2008-05-14 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 15:34 2.6.26-rc2-mm1: oops on ARM while registering GPIO Keys Byron Bradley
2008-05-14 15:52 ` Dmitry Torokhov [this message]
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=20080514115114.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=buytenh@wantstofly.org \
--cc=byron.bbradley@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.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).