linux-kernel - Re: [PATCH v3 16/20] HID: Only dump input if someone is listening

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]

Message-ID: <alpine.LNX.2.00.1209031515450.20709@pobox.suse.cz>
Date:	Mon, 3 Sep 2012 15:17:02 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Henrik Rydberg <rydberg@...omail.se>
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

On Sun, 2 Sep 2012, Henrik Rydberg wrote:

> > 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.

I don't think so.

Let's wait once Dmitry is finished with the input changes, and I can 
either take the set through my tree with his Signed-off-by: on the Input 
patches, or vice-versa.

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/