linux-kernel - Re: [PATCH 3/9] HID: hid, make parsing event driven

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <482AB23C.2090809@gmail.com>
Date:	Wed, 14 May 2008 11:34:52 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Marcel Holtmann <marcel@...tmann.org>
CC:	Jiri Kosina <jkosina@...e.cz>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
	anssi.hannula@...il.com, akpm@...ux-foundation.org,
	Jiri Slaby <jslaby@...e.cz>
Subject: Re: [PATCH 3/9] HID: hid, make parsing event driven

Marcel Holtmann napsal(a):
> Hi Jiri,
> 
>> Next step for complete hid bus, this patch includes:
>> - call parser either from probe or from hid-core if there is no probe.
>> - add ll_driver structure and centralize some stuff there (open, close...)
>> - split and merge usb_hid_configure and hid_probe into several functions
>>   to allow hooks/fixes between them
> 
> has the Bluetooth HIDP changes been tested. You move a lot of code
> around and this might have side effects.

Not really. I was only to test non-hid path (i.e. input) of hidp changes. 
This is why I want it in -mm/-next for some time. If you have some (real) 
bluetooth HID devices, I would be glad if you could test it.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/