[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CC51EC7B5B7F984AA566DC102237848896F62D19@hkdcw-mail1.synaptics-inc.local>
Date: Fri, 16 Nov 2012 09:02:30 +0000
From: Alexandra Chin <alexandra.chin@...synaptics.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
CC: Henrik Rydberg <rydberg@...omail.se>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Linux Input <linux-input@...r.kernel.org>,
Linus Walleij <linus.walleij@...ricsson.com>,
Naveen Kumar Gaddipati <naveen.gaddipati@...ricsson.com>,
Mahesh Srinivasan <msrinivasan@...aptics.com>,
Alex Chang <alex.chang@...synaptics.com>,
Scott Lin <scott.lin@...synaptics.com>,
Christopher Heiny <Cheiny@...aptics.com>
Subject: RE: [RFC] staging: ste_rmi4: merge into the main kernel tree
Hi Dmitry,
> > > Please have Greg commit the patch that Henrik reviewed to staging and
> > > then work with Christopher Heiny group on getting the full featured
> > > driver into mainline.
Thanks for your reminding, final patch has been re-sent to staging
maintainer.
> In this case you need to enumerate the benefits of this driver over
> unified driver and show why the unified driver can't be fixed.
>
> Currently the driver is in mainline (even though the directory is
> staging) and nobody will remove it until another driver is fully
> functional and ready for prime time. But once this happens I do not see
> the benefits of maintaining 2 drivers for the same hardware.
I see. Given that the driver will remain in mainline before generic driver
is ready, currently I will continue to maintain the driver in staging.
Appreciate your response.
Alexandra
--
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