linux-kernel - Re: [PATCHv1] staging: Synaptics RMI4 touchpad driver support

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:	Tue, 2 Nov 2010 16:29:22 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Christopher Heiny <cheiny@...aptics.com>
Cc:	Greg KH <greg@...ah.com>,
	Naveen Kumar G <naveen.gaddipati@...ricsson.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"STEricsson_nomadik_linux@...t.st.com" 
	<STEricsson_nomadik_linux@...t.st.com>
Subject: Re: [PATCHv1] staging: Synaptics RMI4 touchpad driver support

> I must confess that I am seriously confused as to why this patch should 
> be considered for fast tracking into the "real" kernel.  It's based on 

Because its usable, it works and people want to be able to use their
hardware.

> an implementation that wasn't considered suitable for the "real" kernel, 
> and doesn't address the concerns relating to that.  If "merge it now, 
> fix it later" wasn't an acceptable approach previously, is there some 
> compelling reason it is now acceptable?

staging is different to putting it in drivers/input/

> On the other hand, I totally understand frustration with our slow rate 
> of output.  We're trying to produce the best possible code, but this is 
> not happening as quickly as any of us would like.

And in the mean time we've got an acceptable driver that works and which
we are happy to pitch overboard once the masterpiece appears. Until then
people would like to use their hardware.

Alan
--
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/