linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: Naveen Kumar GADDIPATI <naveen.gaddipati@stericsson.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	STEricsson_nomadik_linux <STEricsson_nomadik_linux@list.st.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCHv1] staging: Synaptics RMI4 touchpad driver support
Date: Tue, 2 Nov 2010 08:20:55 -0700	[thread overview]
Message-ID: <20101102152055.GA2104@kroah.com> (raw)
In-Reply-To: <4CD01CD8.3090206@stericsson.com>

On Tue, Nov 02, 2010 at 03:14:48PM +0100, Linus Walleij wrote:
> Greg KH wrote:
> 
> >> +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.
> 
> Well, Alan (on behalf of Ramesh Agarwal) sent out a very similar
> patch (Titled "Synaptics TM1217 Touchscreen Controller driver")
> the other day, and OTOMH that was after discussions with Synaptics
> where they said they were working on a "real" driver (a rather
> complex RMI4 bus driver) and we believe they will fix that sooner
> or later.
> 
> So, until sooner or later happens we thought we'd keep it in staging.
> 
> If you prefer both Alan and we can probably submit our patches for
> inclusion in the proper place.

Yes, please do that.

> A side effect may be that the Synaptics RMI4 people may have trouble
> to merge their driver into input/ since they may be requested to
> refactor the existing drivers to use it rather than merging new stuff,
> putting some burden on their shoulders.

That's the burden of any developer, especially ones that are slower to
get their code released :)

thanks,

greg k-h

  reply	other threads:[~2010-11-02 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1288699725-14405-1-git-send-email-naveen.gaddipati@stericsson.com>
     [not found] ` <20101102140337.GC9387@kroah.com>
2010-11-02 14:14   ` [PATCHv1] staging: Synaptics RMI4 touchpad driver support Linus Walleij
2010-11-02 15:20     ` Greg KH [this message]
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

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=20101102152055.GA2104@kroah.com \
    --to=greg@kroah.com \
    --cc=STEricsson_nomadik_linux@list.st.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-input@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).