From: Luis Henriques <luis.henriques@canonical.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "James Henstridge" <james.henstridge@canonical.com>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
"Fabien André" <fabien.andre@gmail.com>,
"Bastien Nocera" <hadess@hadess.net>
Subject: Re: [appleir] BUG: unable to handle kernel NULL pointer dereference
Date: Thu, 21 Nov 2013 10:13:16 +0000 [thread overview]
Message-ID: <20131121101316.GA3394@hercules.my.domain> (raw)
In-Reply-To: <alpine.LNX.2.00.1311210959170.22082@pobox.suse.cz>
On Thu, Nov 21, 2013 at 09:59:27AM +0100, Jiri Kosina wrote:
> On Thu, 21 Nov 2013, James Henstridge wrote:
>
> > Sorry for the delays in testing out the patch. I have tried a kernel
> > with the patch applied, and can no longer reproduce the oops. The
> > hid-appleir driver appears to be working correctly, generating key
> > press events in response to the remote, and LIRC functions correctly
> > via hiddev.
> >
> > Thanks for the everyone's help with this.
>
> Applied, thanks.
Hi Jiri,
Since this fixes an issue in a 3.11 kernel, could you please tag this
commit for stable>=3.11? If its too late, I can send the request to
stable@ once this patch is merged.
Cheers,
--
Luis
next prev parent reply other threads:[~2013-11-21 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 14:51 [appleir] BUG: unable to handle kernel NULL pointer dereference Luis Henriques
2013-11-06 15:38 ` Jiri Kosina
2013-11-06 17:13 ` Bastien Nocera
2013-11-07 7:52 ` James Henstridge
2013-11-07 15:49 ` Benjamin Tissoires
2013-11-16 0:21 ` Jiri Kosina
2013-11-19 14:33 ` Jiri Kosina
2013-11-21 3:20 ` James Henstridge
2013-11-21 8:59 ` Jiri Kosina
2013-11-21 10:13 ` Luis Henriques [this message]
2013-11-22 12:39 ` Jiri Kosina
2013-11-22 12:52 ` Luis Henriques
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=20131121101316.GA3394@hercules.my.domain \
--to=luis.henriques@canonical.com \
--cc=benjamin.tissoires@redhat.com \
--cc=fabien.andre@gmail.com \
--cc=hadess@hadess.net \
--cc=james.henstridge@canonical.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).