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-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
