From: Chase Douglas <chase.douglas@canonical.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input <linux-input@vger.kernel.org>,
Michael Poole <mdpoole@troilus.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: 35022: hid-magicmouse broken
Date: Tue, 17 May 2011 08:40:24 -0400 [thread overview]
Message-ID: <4DD26CB8.7070409@canonical.com> (raw)
Hi Jiri,
I've received a few emails about the magicmouse driver being broken on
2.6.39:
https://bugzilla.kernel.org/show_bug.cgi?id=35022
It seems hid_output_raw_report() is returning a different (incorrect?)
value than in the past. Do you know what might be going on?
Thanks!
-- Chase
next reply other threads:[~2011-05-17 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 12:40 Chase Douglas [this message]
2011-05-17 12:56 ` 35022: hid-magicmouse broken Jiri Kosina
2011-05-17 19:14 ` Chase Douglas
2011-05-19 11:59 ` Jiri Kosina
2011-05-19 13:13 ` Chase Douglas
2011-05-19 14:54 ` Jiri Kosina
2011-05-19 15:40 ` Chase Douglas
2011-05-19 16:03 ` Jiri Kosina
2011-05-19 18:03 ` Chase Douglas
2011-05-20 8:28 ` Jiri Kosina
2011-05-20 13:04 ` Chase Douglas
2011-05-23 9:04 ` Jiri Kosina
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=4DD26CB8.7070409@canonical.com \
--to=chase.douglas@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=mdpoole@troilus.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).