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]
Date:	Wed, 6 Dec 2006 16:39:50 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Marcel Holtmann <marcel@...tmann.org>,
	Li Yu <raise.sail@...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>
Subject: Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

On Wed, 6 Dec 2006, Dmitry Torokhov wrote:

> If Greg is OK with that I would start with truly mechanical merge (no 
> now data structures, just move the files around) and merge this ASAP, 
> before we hit -rc1 or -rc2 at the latest. Then you can start puling up 
> your changesin the separate git tree.

The first of the 8 patches which currently exist just moves things around 
physically. Just that is not enough, unfortunately, some tweaking is 
needed anyway (static functions, new headers, Kconfig changes, etc), so I 
think it might maybe be better to take the bunch of all 8 patches 
initially as a whole, as they really don't do too intrusive changes to the 
code, and could stay in tree for some testing (though I of course tested 
them to some extent) together.

> Take up Marcel on his suggestion ;) I could set up a tree too but I am 
> afraid I won't have enought time at the moment.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ