linux-kernel - Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

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: <Pine.LNX.4.64.0612061114560.28502@twin.jikos.cz>
Date:	Wed, 6 Dec 2006 11:24:35 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Li Yu <raise.sail@...il.com>
cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Greg Kroah Hartman <greg@...ah.com>,
	linux-usb-devel <linux-usb-devel@...ts.sourceforge.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Vincent Legoll <vincentlegoll@...il.com>,
	"Zephaniah E. Hull" <warp@...allh.com>, liyu <liyu@...ss.com.cn>,
	Marcel Holtmann <marcel@...tmann.org>
Subject: Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

On Wed, 6 Dec 2006, Li Yu wrote:

> 	1. Make hidinput_disconnect_core() be more robust, it can not 
>          break anything even failed to allocate device struct.
> 	2. Thanks new input device driver API, we need not the extra code 
>          for support force-feed device yet, so say bye to 
>          CONFIG_HID_SIMPLE_FF.
> Is this ready to merge? or What still is problem in them? Thanks.

Hi,

actually, I have prepared patches to split the USBHID code in two parts - 
generic HID, which could be hooked by transport-specific HID layers (USB, 
Bluetooth). 

I did not send them to lkml/linux-usb, as they are quite big (mainly 
because a lot of code is being moved around). I am currently trying to 
setup a git repository on kernel.org, hopefully kernel.org people will 
react, so that the patches could be easily put into git repository and be 
available for rewiew and easy merge. After that, they are planned to be 
merged either into Greg's or Andrew's tree. I can send them to you if you 
want.

Do you think that you could wait a little bit more, after the split has 
been done? (it's currently planned approximately after 2.6.20-rc1). It 
seems to me that your patches will apply almost cleanly on top of the 
split patches (you will have to change the pathnames, of course).

Thanks,

-- 
Jiri Kosina
SUSE Labs

-
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/