| 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: <20120902085211.GA604@polaris.bitmath.org> Date: Sun, 2 Sep 2012 10:52:11 +0200 From: "Henrik Rydberg" <rydberg@...omail.se> To: Jiri Kosina <jkosina@...e.cz> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v3 16/20] HID: Only dump input if someone is listening Hi Jiri, > I have applied this one right away, so you can drop it from your series. > The remaining ones I am still about to review (currently travelling). Great, thanks. The notification callback can also be applied if you want. > There is no inter-dependency between the Input and HID ones, and so we can > handle them with Dmitry as two independent Input and HID series, right? Not quite, I am afraid. Some of the overlap has disappeared, true. However, the hid-multitouch patches depend on new variables defined in the input-mt patches, which in turn depend on the input core changes. The hid-multitouch patches will apply (with a tiny merge conflict), but they will not compile. I can split the input-core and hid-core changes into separate sets, and those could be applied separately. The input-mt and bcm5974 will then build on input-core, and hid-multitouch will build on both input-core and hid-core. I am not sure if this helps anyone, though. Thanks, Henrik -- 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