From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Greg KH <greg@kroah.com>
Cc: Naveen Kumar G <naveen.gaddipati@stericsson.com>,
linux-kernel@vger.kernel.org,
STEricsson_nomadik_linux@list.st.com
Subject: Re: [PATCHv1] staging: Synaptics RMI4 touchpad driver support
Date: Tue, 2 Nov 2010 14:06:11 +0000 [thread overview]
Message-ID: <20101102140611.59d40e25@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20101102140337.GC9387@kroah.com>
On Tue, 2 Nov 2010 07:03:37 -0700
Greg KH <greg@kroah.com> wrote:
> On Tue, Nov 02, 2010 at 05:38:45PM +0530, Naveen Kumar G wrote:
> > --- /dev/null
> > +++ b/drivers/staging/ste_rmi4/TODO
> > @@ -0,0 +1,7 @@
> > +TODO
> > +----
> > +
> > +Wait for the official upstream synaptics rmi4 clearpad drivers as promised over the past few months
> > +Merge any device support needed from this driver into it
> > +Delete this driver
>
> Huh?
>
> Why not just add this driver to the kernel tree instead? When the
> "promised" driver then eventually shows up (who is promising it?) then
> delete the thing.
I've suggested that in the past.
> But until then, why is this needed to go into the staging tree? Is
> there any other main reason it should be here and not in the "real" part
> of the kernel?
It's a driver nobody wants to commit to keeping around when there is
eventually a general purpose driver. In other words things like module
names will change.
next prev parent reply other threads:[~2010-11-02 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 12:08 Naveen Kumar G
2010-11-02 14:03 ` Greg KH
2010-11-02 14:06 ` Alan Cox [this message]
2010-11-02 14:22 ` Greg KH
2010-11-02 14:14 ` Linus Walleij
2010-11-02 15:20 ` Greg KH
2010-11-02 15:40 ` Dmitry Torokhov
2010-11-03 18:10 ` Greg KH
2010-11-03 19:07 ` Dmitry Torokhov
2010-11-03 19:19 ` Greg KH
2010-11-03 21:37 ` Arce, Abraham
2010-11-04 4:14 ` Dmitry Torokhov
2010-11-04 5:36 ` Naveen Kumar GADDIPATI
2010-11-04 5:45 ` Arce, Abraham
2010-11-04 5:59 ` Naveen Kumar GADDIPATI
2010-11-04 11:31 ` Dmitry Torokhov
2010-11-02 16:12 ` Christopher Heiny
2010-11-02 16:29 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101102140611.59d40e25@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.gaddipati@stericsson.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®