From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ppsw-50.csi.cam.ac.uk ([131.111.8.150]:36116 "EHLO ppsw-50.csi.cam.ac.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932301Ab0JXSSG (ORCPT ); Sun, 24 Oct 2010 14:18:06 -0400 Message-ID: <4CC479C0.9030607@cam.ac.uk> Date: Sun, 24 Oct 2010 19:24:00 +0100 From: Jonathan Cameron MIME-Version: 1.0 To: Mike Frysinger 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 References: <1287830963-18377-1-git-send-email-vapier@gentoo.org> <4CC320D2.6030300@cam.ac.uk> <4CC413F8.1030908@cam.ac.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.org On 10/24/10 16:58, Mike Frysinger wrote: > On Sun, Oct 24, 2010 at 07:09, Jonathan Cameron wrote: >> 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 >>>>> >>>>> 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. > > they merge cleanly, they just dont compile :p. what tree exactly > contains these changes you're referring to ? > -mike > either linux-next or staging-next branch of http://git.kernel.org/?p=linux/kernel/git/gregkh/staging-next-2.6.git;a=summary The all went in a few weeks back. Personally I just work against Gregs staging-next tree.