public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Chris Hudson <chudson@kionix.com>
Cc: Jean Delvare <khali@linux-fr.org>,
	linux-omap@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [RFC PATCH 1/3] hwmon:driver support for Kionix kxte9 accelerometer
Date: Wed, 11 Nov 2009 14:14:26 +0000	[thread overview]
Message-ID: <4AFAC6C2.8010708@cam.ac.uk> (raw)
In-Reply-To: <4AF9E115.9090603@kionix.com>

Chris Hudson wrote:
> Jean Delvare wrote:
>> On Tue, 10 Nov 2009 15:32:50 -0500, Chris Hudson wrote:
>>  
>>> Thank you for your insight Jonathan.  The driver was originally
>>> written for the 2.6.29 omap-android kernel to facilitate integration
>>> of the kxte9 into customer projects.  Unfortunately, it seems that
>>> things in the kernel have changed since then, but I'm not sure how
>>> much we can change without sacrificing compatibility with the Android
>>> sensor API.  Is there a different place where this driver could go
>>> without requiring significant redesign?
>>>     
>>
>> I don't think a move implies a redesign. You could put exactly the same
>> driver under drivers/misc, drivers/accel, drivers/input or what do I
>> know. I don't want it in drivers/hwmon, but I don't care about anything
>> else.
>>
>>   
> Thank you Jean; I will resubmit the driver for drivers/input/misc if
> that sounds appropriate.  On another note, I accidentally left some
> debug code in place that I will be removing (unless it seems appropriate
> to leave that in for intermediate testing).  Any thoughts on this?
I'd run the code (or a description) quickly past the input maintainer 
Dmitry Torokhov <dmitry.torokhov@gmail.com> before putting any effort into
this.  You certainly don't want to being playing pingpong around the kernel
like one or two other drivers have!

Personally I'd drop debugging unless you have a reason you think there may be
problems.   I'm guessing no one who will do review has one anyway so testing
will be over to you in the short term anyway!  If it's not useful to you anymore
drop it.

Jonathan

  reply	other threads:[~2009-11-11 14:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 18:28 [RFC PATCH 1/3] hwmon:driver support for Kionix kxte9 accelerometer chudson
2009-11-10 18:28 ` [RFC PATCH 2/3] mach-omap2:kxte9 accelerometer support for OMAP ZoomII chudson
2009-11-10 18:28   ` [RFC PATCH 3/3] mach-omap2:mux support for kxte9 accelerometer on " chudson
2009-11-10 18:35 ` [lm-sensors] [RFC PATCH 1/3] hwmon:driver support for Kionix kxte9 accelerometer Jean Delvare
2009-11-10 18:50   ` Chris Hudson
2009-11-10 19:00     ` Jonathan Cameron
2009-11-10 20:32       ` Chris Hudson
2009-11-10 21:39         ` Jean Delvare
2009-11-10 21:54           ` Chris Hudson
2009-11-11 14:14             ` Jonathan Cameron [this message]
2009-11-11 14:21               ` Chris Hudson
2009-11-12 21:10 ` Jonathan Cameron

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=4AFAC6C2.8010708@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=chudson@kionix.com \
    --cc=khali@linux-fr.org \
    --cc=linux-omap@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