On Fri, 21 Mar 2008 16:07:01 -0400, "Dmitry Torokhov" <dmitry.torokhov@gmail.com> said:It would solve my problem, yes. But I'd prefer if joydev and mousedev did not bind to unknown+capabilities, just in case. Looks like bad form to me, and might bite us back later on. We can properly fix all drivers in-tree to have suitable types for joydev and/or mousedev binds, rfkill binds, and so on after all. What did I miss? Are there drivers for some sort of generic device that would be unable to set their type bitfields at runtime? BTW: as far as I can see, type should be a bitfield or a list, to allow a device to have more than one type. Is that fine with you? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh --
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| KAMEZAWA Hiroyuki | Re: 2.6.24-rc3-mm1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jarek Poplawski | Re: [BUG #12364] Re: HTB - very bad precision? HFSC works fine! 2.6.28 |
| Alexey Dobriyan | Re: [GIT]: Networking |
