From: Jonathan Cameron <jic23@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Lars-Peter Clausen <lars@metafoo.de>, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: Drop duplicate forward declaration
Date: Sat, 14 Oct 2017 18:29:50 +0100 [thread overview]
Message-ID: <20171014182950.41f1a61d@archlinux> (raw)
In-Reply-To: <e46d722561e1d2288ff8f421332c0499e38a2dcb.1507651877.git.lukas@wunner.de>
On Tue, 10 Oct 2017 18:15:34 +0200
Lukas Wunner <lukas@wunner.de> wrote:
> Commit 5f420b42079c ("staging:iio: Add extended IIO channel info") added
> a forward declaration for struct iio_dev to <linux/iio/iio.h> but forgot
> to remove an existing forward declaration further down originating from
> commit 7ae8cf627558 ("staging: iio: chrdev.h rationalization").
>
> Cc: Lars-Peter Clausen <lars@metafoo.de>
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.
Thanks,
Jonathan
> ---
> include/linux/iio/iio.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index 50cae85..20b6134 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -365,7 +365,6 @@ static inline bool iio_channel_has_available(const struct iio_chan_spec *chan,
> #define INDIO_MAX_RAW_ELEMENTS 4
>
> struct iio_trigger; /* forward declaration */
> -struct iio_dev;
>
> /**
> * struct iio_info - constant information about device
prev parent reply other threads:[~2017-10-14 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 16:15 [PATCH] iio: Drop duplicate forward declaration Lukas Wunner
2017-10-14 17:29 ` 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=20171014182950.41f1a61d@archlinux \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=lukas@wunner.de \
/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).