From: Josip Rodin <joy@debbugs.entuzijast.net>
To: Nestor Lopez Casado <nlopezcasad@logitech.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
685360@bugs.debian.org, john.ettedgui@gmail.com,
barz621@gmail.com, dh.herrmann@googlemail.com
Subject: Re: [PATCH 1/1] HID: Fix missing Unifying device issue
Date: Thu, 27 Sep 2012 09:04:26 +0200 [thread overview]
Message-ID: <20120927070426.GA27734@entuzijast.net> (raw)
In-Reply-To: <CAE7qMroQOxo7kci7roLbS5HXjpkyhRi=cj1WCoYtAPB328xNQg@mail.gmail.com>
On Mon, Sep 24, 2012 at 11:30:28AM +0200, Nestor Lopez Casado wrote:
> Josip, this is a different issue from the one addressed with the patch.
>
> 1) Can you try it on a 3.2 kernel ?
I can try that too, I'll let you know how it went.
(Unfortunately the machine is in the same room with a crib, so I don't
get a lot of time slots for testing. *shrug* :)
> 2) The problem you describe, does it happen all the time ?
Yes. The keyboard simply stopped working after I upgraded to Linux 3.2.
It works fine under 3.1 and earlier, and under Windows.
--
2. That which causes joy or happiness.
next prev parent reply other threads:[~2012-09-27 7:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 10:21 [PATCH 1/1] HID: Fix missing Unifying device issue Nestor Lopez Casado
2012-09-22 7:50 ` Jiri Kosina
2012-09-22 20:47 ` Jiri Kosina
2012-09-23 10:23 ` Bug#685360: " Josip Rodin
2012-09-24 9:30 ` Nestor Lopez Casado
2012-09-27 7:04 ` Josip Rodin [this message]
2012-09-27 18:56 ` Josip Rodin
2012-09-28 7:57 ` Bug#685360: " Nestor Lopez Casado
2012-10-08 19:42 ` Bug#685360: " Apostolos Bartziokas
2012-10-09 10:15 ` [PATCH 1/1] " Nestor Lopez Casado
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=20120927070426.GA27734@entuzijast.net \
--to=joy@debbugs.entuzijast.net \
--cc=685360@bugs.debian.org \
--cc=barz621@gmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=dh.herrmann@googlemail.com \
--cc=jkosina@suse.cz \
--cc=john.ettedgui@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nlopezcasad@logitech.com \
/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).