From: "Alexey Klimov" <klimov.linux@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>, Jiri Kosina <jkosina@suse.cz>
Cc: Tobias Lorenz <tobias.lorenz@gmx.net>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
linux-input@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: next: 6a13378a5 (Don't allow KWorld radio...) is broken
Date: Thu, 13 Nov 2008 05:24:24 +0300 [thread overview]
Message-ID: <208cbae30811121824g2e2d4f3bvf2c982c9f54b30a2@mail.gmail.com> (raw)
In-Reply-To: <491B3E90.5020307@gmail.com>
On Wed, Nov 12, 2008 at 11:37 PM, Jiri Slaby <jirislaby@gmail.com> wrote:
> There is a difference between hid_blacklist and hid_ignore_list. One forbids
> generic hid driver to bind the device, while the other forces usbhid to release
> the device and move hands away from it.
I figured that out and remembered that this thing needed to be fixed and
then got side-tracked by other things. Sorry.
On Thu, Nov 13, 2008 at 3:33 AM, Jiri Kosina <jkosina@suse.cz> wrote:
> Alexey, did you actually test it?
> I'd prefer taking this through my tree, if it doesn't impose any problem
> on your side. Could you please fix it up and resend?
It good thing to do. May i make patch against current kernel tree (rc4-git3) ?
I also going to make patch for radio-mr800 that has wrong hidquirks too.
I can send now, because this two patches ready.
--
Best regards, Klimov Alexey
next prev parent reply other threads:[~2008-11-13 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 20:37 next: 6a13378a5 (Don't allow KWorld radio...) is broken Jiri Slaby
2008-11-13 0:33 ` Jiri Kosina
2008-11-13 2:44 ` [PATCH 1/2] hid: fix kworld fm700 radio hidquirks Alexey Klimov
2008-11-13 2:44 ` [PATCH 2/2] hid: fix radio-mr800 hidquirks Alexey Klimov
2008-11-13 13:30 ` next: 6a13378a5 (Don't allow KWorld radio...) is broken Mauro Carvalho Chehab
2008-11-13 2:24 ` Alexey Klimov [this message]
2008-11-13 9:37 ` 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=208cbae30811121824g2e2d4f3bvf2c982c9f54b30a2@mail.gmail.com \
--to=klimov.linux@gmail.com \
--cc=jirislaby@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=tobias.lorenz@gmx.net \
/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).