From: Jonathan Cameron <jic23@cam.ac.uk>
To: michael.hennerich@analog.com
Cc: linux-iio@vger.kernel.org, drivers@analog.com,
device-drivers-devel@blackfin.uclinux.org
Subject: Re: [PATCH] IIO-onwards: TRIGGER: iio-trig-bfin-timer: Fix build issues
Date: Thu, 21 Apr 2011 09:55:43 +0100 [thread overview]
Message-ID: <4DAFF10F.60708@cam.ac.uk> (raw)
In-Reply-To: <1303310503-4137-1-git-send-email-michael.hennerich@analog.com>
On 04/20/11 15:41, michael.hennerich@analog.com wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
>
> Fix typos
Oops ;) Should probably set myself up a blackfin toolchain at some point...
> select BFIN_GPTIMERS
>
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
> ---
> drivers/staging/iio/trigger/Kconfig | 1 +
> drivers/staging/iio/trigger/iio-trig-bfin-timer.c | 4 ++--
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/iio/trigger/Kconfig b/drivers/staging/iio/trigger/Kconfig
> index c33777e..b8abf54 100644
> --- a/drivers/staging/iio/trigger/Kconfig
> +++ b/drivers/staging/iio/trigger/Kconfig
> @@ -31,6 +31,7 @@ config IIO_SYSFS_TRIGGER
> config IIO_BFIN_TMR_TRIGGER
> tristate "Blackfin TIMER trigger"
> depends on BLACKFIN
> + select BFIN_GPTIMERS
> help
> Provides support for using a Blackfin timer as IIO triggers.
> If unsure, say N (but it's safe to say "Y").
> diff --git a/drivers/staging/iio/trigger/iio-trig-bfin-timer.c b/drivers/staging/iio/trigger/iio-trig-bfin-timer.c
> index 096559d..43b3605 100644
> --- a/drivers/staging/iio/trigger/iio-trig-bfin-timer.c
> +++ b/drivers/staging/iio/trigger/iio-trig-bfin-timer.c
> @@ -116,7 +116,7 @@ static const struct attribute_group iio_bfin_tmr_trigger_attr_group = {
> .attrs = iio_bfin_tmr_trigger_attrs,
> };
>
> -static const sturc attribute_group *iio_bfin_tmr_trigger_attr_groups[] = {
> +static const struct attribute_group *iio_bfin_tmr_trigger_attr_groups[] = {
> &iio_bfin_tmr_trigger_attr_group,
> NULL
> };
> @@ -176,7 +176,7 @@ static int __devinit iio_bfin_tmr_trigger_probe(struct platform_device *pdev)
>
> st->trig->private_data = st;
> st->trig->owner = THIS_MODULE;
> - trig->dev.groups = iio_bfin_tmr_trigger_attr_groups;
> + st->trig->dev.groups = iio_bfin_tmr_trigger_attr_groups;
> ret = iio_trigger_register(st->trig);
> if (ret)
> goto out2;
prev parent reply other threads:[~2011-04-21 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 14:41 [PATCH] IIO-onwards: TRIGGER: iio-trig-bfin-timer: Fix build issues michael.hennerich
2011-04-21 8:55 ` 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=4DAFF10F.60708@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=drivers@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=michael.hennerich@analog.com \
/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