All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-iio@vger.kernel.org, device-drivers-devel@blackfin.uclinux.org
Subject: Re: [Device-drivers-devel] [PATCH 1/3] staging: iio: new adis16201 driver
Date: Sun, 24 Oct 2010 12:09:44 +0100	[thread overview]
Message-ID: <4CC413F8.1030908@cam.ac.uk> (raw)
In-Reply-To: <AANLkTim+czzJ__zuMCpjv4nV6rOJ9n50_4MR2VkQk6T_@mail.gmail.com>

On 10/23/10 21:32, Mike Frysinger wrote:
> On Sat, Oct 23, 2010 at 13:52, Jonathan Cameron wrote:
>> On 10/23/10 11:49, Mike Frysinger wrote:
>>> From: Barry Song <barry.song@analog.com>
>>>
>>> IIO driver for dual Axis Accelerometer/inclinometer adis16201 parts.
>>
>> Please check these for building against staging next.  There have been
>> a couple of cleanup and abi fix series merged since the tree you are
>> working against (at least I'm guessing that's what causes...
> 
> testing against current mainline
Unfortunately that isn't where they are going to merge.  The change
required won't be huge, but Greg isn't going to take them if they
don't merge cleanly.

Still, fine to review them against mainline.  

Thanks,

Jonathan

  reply	other threads:[~2010-10-24 11:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-23 10:49 [PATCH 1/3] staging: iio: new adis16201 driver Mike Frysinger
2010-10-23 10:49 ` [PATCH 2/3] staging: iio: new adis16203 driver Mike Frysinger
2010-10-23 17:22   ` Jonathan Cameron
2010-10-23 10:49 ` [PATCH 3/3] staging: iio: new adis16204 driver Mike Frysinger
2010-10-23 17:45   ` Jonathan Cameron
2010-10-23 17:04 ` [PATCH 1/3] staging: iio: new adis16201 driver Jonathan Cameron
2010-10-23 17:21   ` Jonathan Cameron
2010-10-23 17:52 ` Jonathan Cameron
2010-10-23 20:32   ` [Device-drivers-devel] " Mike Frysinger
2010-10-24 11:09     ` Jonathan Cameron [this message]
2010-10-24 15:58       ` Mike Frysinger
2010-10-24 18:24         ` Jonathan Cameron
2010-10-24 18:22           ` Mike Frysinger
2010-10-24 18:43             ` Jonathan Cameron
2010-10-29  1:30             ` Greg KH
2010-10-24 18:36           ` Michael Frysinger

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=4CC413F8.1030908@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.