From: Onkalo Samu <samu.p.onkalo@nokia.com>
To: "ext Éric Piel" <eric.piel@tremplin-utc.net>,
"Trisal, Kalhan" <kalhan.trisal@intel.com>
Cc: Jonathan Cameron <Jonathan.Cameron@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>,
Jean Delvare <khali@linux-fr.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH 0/2] LIS3LV02D I2C driver
Date: Tue, 13 Oct 2009 13:13:33 +0300 [thread overview]
Message-ID: <1255428813.3974.9.camel@4fid08082> (raw)
In-Reply-To: <4ACCCF48.5090005@tremplin-utc.net>
On Wed, 2009-10-07 at 19:26 +0200, ext Éric Piel wrote:
> Op 07-10-09 19:01, Éric Piel schreef:
> > Op 07-10-09 18:31, Jonathan Cameron schreef:
> >> Just a quick heads up wrt overlapping work.
> >>
> >> For the i2c support Kalhan Trisal has been posting patches for i2c
> >> support for this
> >> driver to the lm-sensors list for some time and the latest version of that
> >> set is also pretty clean.
> > You mean this post, right?
> > http://lists.lm-sensors.org/pipermail/lm-sensors/2009-August/026505.html
> > "Accelerometer driver for STMicroeletronics-LIS331DL-three-axis-digital"
> > Thanks for the heads up, I had never heard of this driver before.
>
> :
> > Kalhan, would
> > you mind having a look at the patch from Samu, and see what is required
> > to get your LIS331DL working with the lis3lv02d driver? It should be
> > very little and avoid duplication of efforts :-)
> Ah, bah,
> I see you have actually already more or less done this!
> http://lists.lm-sensors.org/pipermail/lm-sensors/2009-October/026840.html
> "I2C glue layer for lis3lv02d STMicroelectronics digital accelerometer"
>
> The main thing you forgot to do with this patch was to CC the maintainer
> of the driver (AKA me) ;-)
>
> Anyway, this version is _very_ close to the one from Samu. It has just
> all the basics, really clean! Samu has already added some nifty things
> (like changing the axis conversion, support for suspend...). So it
> should _really_ easy to converge :-) As Samu's patch is already in
> Andrew's queue, I think it's simpler to leave it as it, and just to keep
> my request to you, Kalhan, to check that it works for your hardware as
> well.
Hi Kalhan,
Have you been able to test my patch if it works also for your HW?
http://marc.info/?l=linux-kernel&m=125472767421625&w=2
http://marc.info/?l=linux-kernel&m=125472767421629&w=2
http://marc.info/?l=linux-kernel&m=125472767421639&w=2
Br,
Samu
next prev parent reply other threads:[~2009-10-13 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 10:06 [RFC][PATCH 0/2] LIS3LV02D I2C driver Samu Onkalo
2009-10-01 10:06 ` [PATCH 1/2] LIS3LV02D: axis remap, irq and resource setup / release added to platform data Samu Onkalo
2009-10-01 10:06 ` [PATCH 2/2] LIS3LV02D: I2C support Samu Onkalo
2009-10-02 8:20 ` Éric Piel
2009-10-07 16:31 ` [RFC][PATCH 0/2] LIS3LV02D I2C driver Jonathan Cameron
2009-10-07 17:01 ` Éric Piel
2009-10-07 17:20 ` Jonathan Cameron
2009-10-07 17:26 ` Éric Piel
2009-10-13 10:13 ` Onkalo Samu [this message]
2009-10-13 10:20 ` Trisal, Kalhan
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=1255428813.3974.9.camel@4fid08082 \
--to=samu.p.onkalo@nokia.com \
--cc=Jonathan.Cameron@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=kalhan.trisal@intel.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
/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