Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Barry Song <21cnbao@gmail.com>
Cc: linux-iio@vger.kernel.org, Barry Song <Barry.Song@analog.com>
Subject: Re: [PATCH RFC] staging:iio: adis16209 accelerometer driver initial import
Date: Thu, 06 May 2010 11:23:59 +0100	[thread overview]
Message-ID: <4BE298BF.2080400@cam.ac.uk> (raw)
In-Reply-To: <l2w3c17e3571005060233yf53496f7s7598fcc9ab72be85@mail.gmail.com>

On 05/06/10 10:33, Barry Song wrote:
> Thanks a lot for your review and good comments. I have updated
> adis16209 and adis16240(which has been tested too) according to your
> comment. I am 100% sure we will pull new iio features to our tree. But
> i am busy on testing adis16220/260/350, so if possible, i still need
> your help to merge them into 2.6.35 just like adis16300/400 for the
> moment.
You are welcome.  Post the updated patches here as and when they are ready.
It would be great to get a nasty large driver set merged for 2.6.35 as
iio could do with exposure and publicity that will generate!

All the reponses look good to me, so looking forward to seeing the
updated driver.  I'll have a think about the best fix in the core for the
current need to register an empty event attribute group.  It is kind of
a driver bug, but then the stage you are at is pretty typical for a driver
still under development so it would be nice if it didn't cause a problem!

As long as the patches are new drivers or fixs, I'd imaging Greg will be keep taking them
until at least the beginning of the merge window (probably a couple of
weeks time).  As staging usually merges pretty late, we may well sneak
in a few more when the window is open, but that's entirely up to Greg.

Jonathan

  reply	other threads:[~2010-05-06 10:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 15:23 [PATCH RFC] staging:iio: adis16209 accelerometer driver initial import Jonathan Cameron
2010-05-05 20:13 ` Jonathan Cameron
2010-05-06  9:33   ` Barry Song
2010-05-06 10:23     ` Jonathan Cameron [this message]
2010-05-06 11:34       ` 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=4BE298BF.2080400@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=21cnbao@gmail.com \
    --cc=Barry.Song@analog.com \
    --cc=linux-iio@vger.kernel.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