linux-kernel - Re: [PATCH 4/5] HID: autoload hid-multitouch as needed

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: <620FFED4-6D6D-4F70-8674-D054C5E3B38A@enac.fr>
Date:	Tue, 13 Mar 2012 19:14:56 +0100
From:	Stéphane Chatty <chatty@...c.fr>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Marcel Holtmann <marcel@...tmann.org>,
	Henrik Rydberg <rydberg@...omail.se>,
	"benjamin.tissoires" <benjamin.tissoires@...il.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
	"Gustavo F. Padovan" <padovan@...fusion.mobi>,
	linux-bluetooth@...r.kernel.org
Subject: Re: [PATCH 4/5] HID: autoload hid-multitouch as needed


Le 13 mars 2012 à 17:13, Jiri Kosina wrote:

> On Tue, 13 Mar 2012, Stéphane Chatty wrote:
>> 
>> Very useful clarification, thanks. Now, I guess I understand why Marcel 
>> wants to keep hidp in bluetooth/. And, to be honest, things would have 
>> been clearer to me when I explored the handling of the USB/HID class if 
>> I had found a hid (or usbhid) directory in usb/ rather than a usbhid 
>> subdirectory in hid/: it did not make the above situation very obvious 
>> to me. Don't you think we could go along with Marcel and move usbhid to 
>> usb/?
> 
> It seemed to be convenient back then, and it's still convenient for me in 
> some sense, as I am maintaining both HID core and USB HID, but bluetooth 
> guys are maintaining the bluetooth transport.
> 
> But I don't have strong opinion either way, I can as well move usbhid to 
> drivers/usb and maintain it there (will need to talk to Greg about it 
> first of course). But frankly, I don't see it making things magically 
> clear for everyone :)


I agree it's neither very important nor a magic bullet. But this confused at least one person (me) when exploring the code for the first time :-)

St.

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