| 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
| ||
|
Message-ID: <20070115183207.GA6792@suse.cz> Date: Mon, 15 Jan 2007 19:32:07 +0100 From: Vojtech Pavlik <vojtech@...e.cz> To: Jiri Kosina <jikos@...os.cz> Cc: Simon Budig <simon@...ig.de>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2.6.19] USB HID: proper LED-mapping (support for SpaceNavigator) On Mon, Jan 15, 2007 at 05:44:26PM +0100, Jiri Kosina wrote: > On Mon, 15 Jan 2007, Simon Budig wrote: > > > > thanks for the patch. It seems that it is based on pre-2.6.20-rc1 kernel > > > (this is where the USBHID split happened and generic HID layer was > > > introduced). Could you please rebase it against newer version of kernel > > > and resend it? > > I've updated the patch, will submit it to the list in a few minutes. > > I got it, thanks. > > > > All your changes happen to be in the transport-independent code, so it > > > seems that this would be rather trivial task - probably only pathnames > > > (and diff offsets) will change - your changes should now go to > > > drivers/hid/hid-*, not drivers/usb/input/hid-*. > > Yeah, it was easy to port over. Did the hid-debug stuff disappear > > completely? What would I use instead? > > No, it didn't disappear, it was just moved to include/linux/hid-debug.h. Do you think that makes sense? It's code, not a header file. > Should I wait for an updated patch that uses hid-debug.h again? -- Vojtech Pavlik Director 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/
Powered by blists - more mailing lists