linux-kernel - Re: [RFC v2 0/10] hid-multitouch: a first step towards multitouch unification

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.1101071102390.26685@pobox.suse.cz>
Date:	Fri, 7 Jan 2011 11:03:01 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Benjamin Tissoires <benjamin.tissoires@...c.fr>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Henrik Rydberg <rydberg@...omail.se>,
	Stephane Chatty <chatty@...c.fr>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC v2 0/10] hid-multitouch: a first step towards multitouch
 unification

On Fri, 7 Jan 2011, Benjamin Tissoires wrote:

> >> > In case the patchset doesn't impose danger of regressions for already
> >> > existing devices, we could merge this new 'unified' driver only for newly
> >> > supported devices, and finish the unification in 2.6.39.
> >>
> >> Yep, let's merge the dirver and all new devices in this round and then
> >> get ready to convert already supported devices in next window.
> >
> > Fully agreed, as I have written elsewhere already.
> >
> > Benjamin, when do you expect to have the patches for .38 ready? The merge
> > window is already open, so that I could schedule the merges properly.
> 
> I'm doing my best to have the v3 today with only the 3 new devices.
> After, we may have to find a consensus for the not ideal
> implementation.

That would be excellent, and will allow me to prepare the merge over the 
weekend.

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/