linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Hsu <matt@0xlab.org>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com,
	Samu Onkalo <samu.p.onkalo@nokia.com>,
	Eric Piel <eric.piel@tremplin-utc.net>,
	"Trisal, Kalhan" <kalhan.trisal@intel.com>,
	LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: Duplicated driver for LIS302-like device.
Date: Mon, 14 Dec 2009 11:29:18 +0800	[thread overview]
Message-ID: <4B25B10E.1010409@0xlab.org> (raw)
In-Reply-To: <4B2241D0.3050504@cam.ac.uk>

Jonathan Cameron wrote:
> Hi Matt
>   
> Gah, Not again!  So far we have had two patch sets implementing just
> this.  Looking at the latest from Samu, Eric's patch has been sent on
> to Andrew Morton for the current merge window (and is listed as being in
> his mm tree).  May even have merged since I last pulled mainline.
>
> You have my sympathies as the whole duplicating work thing happens to
> us all from time to time.  The answer is as ever, post early and post
> often to the relevant mailing lists. (though of course hardly anyone
> actually keeps to this!)
>   
    Hi Jonathan,

    Thanks for your information.
    Previously, I only went through input subsystem instead of lm-sensors.
    And now the upstream driver seems to be implemented and merged. I 
will cherry pick them into 0xlab kernel repository.

    Cheers,
    Matt
> I've cc'd in everyone I know has an interest in this driver for any
> thing else they might want to add.
>
> Jonathan
>   


      parent reply	other threads:[~2009-12-14  3:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11  2:52 Duplicated driver for LIS302-like device Matt Hsu
2009-12-11 12:57 ` Jonathan Cameron
2009-12-11 13:16   ` Éric Piel
2009-12-14  3:57     ` Matt Hsu
2009-12-14  3:29   ` Matt Hsu [this message]

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=4B25B10E.1010409@0xlab.org \
    --to=matt@0xlab.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eric.piel@tremplin-utc.net \
    --cc=jic23@cam.ac.uk \
    --cc=kalhan.trisal@intel.com \
    --cc=linux-input@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=samu.p.onkalo@nokia.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).