From: Amit Kucheria <amit.kucheria@verdurent.com>
To: Chris Hudson <chudson@kionix.com>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Driver Merge Questions
Date: Mon, 9 Nov 2009 19:09:00 +0200 [thread overview]
Message-ID: <20091109170900.GA1773@smtp.gmail.com> (raw)
In-Reply-To: <4AF82D27.2010705@kionix.com>
On 09 Nov 09, Chris Hudson wrote:
> Hello Amit,
>
> Thank you for the information.
>
> The driver is just about finished actually; I was going to do some
> final testing and pull and submit the patches today. I read the
> lkml.org source and it definitely seems like things are in a state
> of limbo at the moment (well, as of a few months ago) with regard to
> sensor drivers. So, should I submit the code as-is and work on
> changing it as necessary with the help of the community, or do I
> step back and modify for the iio subsystem before submission?
> Alternatively, since the code was originally written for the 2.6.29
> Android kernel, should I submit the current version of the driver to
> that branch first? Please let me know.
Hi Chris,
No harm is submitting a patch for a hwmon-based driver against mainline
2.6.32-rc6 to LKML (cc the requisite maintainers). It might help get review on
obvious issues, if any.
But be prepared to modify the driver to use IIO. I just modified a driver to
use IIO and isn't that hard - probably an afternoon's work.
Regards,
Amit
--
-------------------------------------------------------------------------
Amit Kucheria, Kernel Developer, Verdurent
-------------------------------------------------------------------------
prev parent reply other threads:[~2009-11-09 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 14:40 Driver Merge Questions Chris Hudson
2009-11-03 16:58 ` Tony Lindgren
2009-11-09 9:26 ` Amit Kucheria
2009-11-09 12:07 ` Amit Kucheria
2009-11-09 14:54 ` Chris Hudson
2009-11-09 17:09 ` Amit Kucheria [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=20091109170900.GA1773@smtp.gmail.com \
--to=amit.kucheria@verdurent.com \
--cc=chudson@kionix.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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