From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, rdunlap@infradead.org, denis.ciocca@st.com
Subject: Re: [PATCH 0/2] iio:st_sensors more fixes when !IIO_CONFIG_TRIGGER
Date: Sat, 09 Feb 2013 15:25:13 +0000 [thread overview]
Message-ID: <51166A59.6090503@kernel.org> (raw)
In-Reply-To: <1360406967-25026-1-git-send-email-jic23@kernel.org>
On 02/09/2013 10:49 AM, Jonathan Cameron wrote:
> Here is how I would suggest dealing with the issues pointed out by
> Randy when buildling without trigger support.
>
Applied to togreg branch of iio.git
> Jonathan
>
> Jonathan Cameron (2):
> iio:triggers Protect functions in triggers.h from use when not
> compiled
> iio:st_sensors fix build when !CONFIG_IIO_TRIGGER
>
> drivers/iio/accel/st_accel_core.c | 9 +++++++--
> drivers/iio/accel/st_accel_i2c.c | 1 -
> drivers/iio/accel/st_accel_spi.c | 1 -
> drivers/iio/gyro/st_gyro_core.c | 9 +++++++--
> drivers/iio/gyro/st_gyro_i2c.c | 1 -
> drivers/iio/gyro/st_gyro_spi.c | 1 -
> drivers/iio/magnetometer/st_magn_core.c | 1 -
> drivers/iio/magnetometer/st_magn_i2c.c | 1 -
> drivers/iio/magnetometer/st_magn_spi.c | 1 -
> include/linux/iio/trigger.h | 5 +++++
> 10 files changed, 19 insertions(+), 11 deletions(-)
>
next prev parent reply other threads:[~2013-02-09 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 10:49 [PATCH 0/2] iio:st_sensors more fixes when !IIO_CONFIG_TRIGGER Jonathan Cameron
2013-02-09 10:49 ` [PATCH 1/2] iio:triggers Protect functions in triggers.h from use when not compiled Jonathan Cameron
2013-02-09 10:49 ` [PATCH 2/2] iio:st_sensors fix build when !CONFIG_IIO_TRIGGER Jonathan Cameron
2013-02-09 11:53 ` Denis Ciocca
2013-02-09 15:24 ` Jonathan Cameron
2013-02-09 15:25 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-09 16:54 [PATCH 0/2] iio:st_sensors more fixes when !IIO_CONFIG_TRIGGER Jonathan Cameron
2013-02-09 16:55 ` 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=51166A59.6090503@kernel.org \
--to=jic23@kernel.org \
--cc=denis.ciocca@st.com \
--cc=linux-iio@vger.kernel.org \
--cc=rdunlap@infradead.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