From: Pengyu Ma <pengyu.ma@windriver.com>
To: <jic23@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: declare struct to fix warning
Date: Thu, 30 Jul 2015 17:26:47 +0800 [thread overview]
Message-ID: <55B9EDD7.4@windriver.com> (raw)
In-Reply-To: <1438247937-29955-1-git-send-email-pengyu.ma@windriver.com>
Since my email doesn't subscribe lkml, I will send again with my gmail
Pengyu
On 07/30/2015 05:18 PM, Pengyu Ma wrote:
> When compile iio related driver the following warning shown:
>
> include/linux/iio/trigger.h:35:34: warning: 'struct iio_trigger'
> declared inside parameter list
> int (*set_trigger_state)(struct iio_trigger *trig, bool state);
>
> include/linux/iio/trigger.h:38:18: warning: 'struct iio_dev'
> declared inside parameter list
> struct iio_dev *indio_dev);
>
> 1st warning: 'struct iio_trigger' was used before declaration;
> 2nd warning: 'struct iio_dev' was used without including head file.
>
> Signed-off-by: Pengyu Ma <pengyu.ma@windriver.com>
> ---
> include/linux/iio/trigger.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/linux/iio/trigger.h b/include/linux/iio/trigger.h
> index 68f46cd..cbe4286 100644
> --- a/include/linux/iio/trigger.h
> +++ b/include/linux/iio/trigger.h
> @@ -9,6 +9,7 @@
> #include <linux/irq.h>
> #include <linux/module.h>
> #include <linux/atomic.h>
> +#include <linux/iio/iio.h>
>
> #ifndef _IIO_TRIGGER_H_
> #define _IIO_TRIGGER_H_
> @@ -18,6 +19,8 @@ struct iio_subirq {
> bool enabled;
> };
>
> +struct iio_trigger; /* forward declaration */
> +
> /**
> * struct iio_trigger_ops - operations structure for an iio_trigger.
> * @owner: used to monitor usage count of the trigger.
next prev parent reply other threads:[~2015-07-30 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 9:18 [PATCH] iio: declare struct to fix warning Pengyu Ma
2015-07-30 9:26 ` Pengyu Ma [this message]
2015-08-02 9:47 ` Lars-Peter Clausen
-- strict thread matches above, loose matches on Subject: below --
2015-07-30 9:28 Aaron Ma
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=55B9EDD7.4@windriver.com \
--to=pengyu.ma@windriver.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).