On 09/18/10 16:48, matthias wrote: > Hi Jonathan, > > sorry for not answering yet. I was on vacation and next week I won't > be able to test the driver. Will try to do it asap.... > > Matthias Hi Matthias, I'm afraid quite a bit has changed over the last few weeks. Feel free to test this patch set. The changes since then are merely renames of a couple of attributes and a lot of stuff for event handling that doesn't effect this driver. If not, I'm hosting a *temporary* git tree with all my various queued up changes at: http://git.kernel.org/?p=linux/kernel/git/jic23/iio_temp.git Seems excessive to post this set again until I hear back from you! Thanks, Jonathan p.s. Switched to drivers@xxxxxxxxxx address as that now seems to work. > > 2010/9/18 Jonathan Cameron <jic23@xxxxxxxxx>: >> On 09/06/10 16:16, Jonathan Cameron wrote: >>> Mainly a rebase, but a couple of attribute naming fixes as well. >>> >>> Note I don't have one of these so if anyone could test that would >>> be great! >>> >>> Signed-off-by: Jonathan Cameron <jic23@xxxxxxxxx> >>> >>> Jonathan Cameron (2): >>> staging:iio:adis16260 add id table support >>> staging:iio:adis16260 add suppport for adis16255 and adis16250. >>> >>> drivers/staging/iio/gyro/Kconfig | 8 +- >>> drivers/staging/iio/gyro/adis16260.h | 3 + >>> drivers/staging/iio/gyro/adis16260_core.c | 139 ++++++++++++++------ >>> drivers/staging/iio/gyro/adis16260_platform_data.h | 19 +++ >>> drivers/staging/iio/gyro/gyro.h | 9 ++ >>> 5 files changed, 136 insertions(+), 42 deletions(-) >>> create mode 100644 drivers/staging/iio/gyro/adis16260_platform_data.h >>> >>> >> Whilst I haven't tested these (don't have the hardware) I don't think there >> is anything controversial, so my intent is to push these to Greg before the >> next merge window. This is primarily to remove the duplication we currently >> have with two drivers that effectively cover the same parts. >> >> Thanks, >> >> Jonathan >> > > > -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
