From: Jonathan Cameron <jic23@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Ge Gao <ggao@invensense.com>
Subject: Re: [PATCH] iio/imu: inv_mpu6050 depends on IIO_BUFFER
Date: Sat, 02 Mar 2013 16:32:34 +0000 [thread overview]
Message-ID: <513229A2.6070700@kernel.org> (raw)
In-Reply-To: <51322924.7010001@kernel.org>
On 03/02/2013 04:30 PM, Jonathan Cameron wrote:
> On 03/01/2013 03:21 PM, Guenter Roeck wrote:
>> Fix:
>>
>> drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c: In function ‘inv_mpu6050_read_fifo’:
>> drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c:176:3: error: implicit declaration of
>> function ‘iio_push_to_buffers’ [-Werror=implicit-function-declaration]
>>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> Thanks, applied to togreg branch of iio.git
sorry I mean the fixes-togreg branch of iio.git
>
>> ---
>> drivers/iio/imu/inv_mpu6050/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/iio/imu/inv_mpu6050/Kconfig b/drivers/iio/imu/inv_mpu6050/Kconfig
>> index b5cfa3a..361b232 100644
>> --- a/drivers/iio/imu/inv_mpu6050/Kconfig
>> +++ b/drivers/iio/imu/inv_mpu6050/Kconfig
>> @@ -5,6 +5,7 @@
>> config INV_MPU6050_IIO
>> tristate "Invensense MPU6050 devices"
>> depends on I2C && SYSFS
>> + select IIO_BUFFER
>> select IIO_TRIGGERED_BUFFER
>> help
>> This driver supports the Invensense MPU6050 devices.
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-03-02 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 15:21 [PATCH] iio/imu: inv_mpu6050 depends on IIO_BUFFER Guenter Roeck
2013-03-02 16:30 ` Jonathan Cameron
2013-03-02 16:32 ` Jonathan Cameron [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=513229A2.6070700@kernel.org \
--to=jic23@kernel.org \
--cc=ggao@invensense.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux@roeck-us.net \
/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