From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: Remove trailing ; from function definitions
Date: Sat, 31 Aug 2013 19:16:16 +0100 [thread overview]
Message-ID: <522232F0.2020503@kernel.org> (raw)
In-Reply-To: <1377040517-11928-1-git-send-email-pmeerw@pmeerw.net>
I thought we'd killed off all of these ages ago.
Good find and applied to iio.git togreg branch.
Our first patch for the 3.13 cycle.
On 08/21/13 00:15, Peter Meerwald wrote:
> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
> ---
> include/linux/iio/iio.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index 45a99ef..c8e94a8 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -458,7 +458,7 @@ static inline void iio_device_put(struct iio_dev *indio_dev)
> {
> if (indio_dev)
> put_device(&indio_dev->dev);
> -};
> +}
>
> /**
> * dev_to_iio_dev() - Get IIO device struct from a device struct
> @@ -565,7 +565,7 @@ static inline bool iio_buffer_enabled(struct iio_dev *indio_dev)
> {
> return indio_dev->currentmode
> & (INDIO_BUFFER_TRIGGERED | INDIO_BUFFER_HARDWARE);
> -};
> +}
>
> /**
> * iio_get_debugfs_dentry() - helper function to get the debugfs_dentry
> @@ -575,12 +575,12 @@ static inline bool iio_buffer_enabled(struct iio_dev *indio_dev)
> static inline struct dentry *iio_get_debugfs_dentry(struct iio_dev *indio_dev)
> {
> return indio_dev->debugfs_dentry;
> -};
> +}
> #else
> static inline struct dentry *iio_get_debugfs_dentry(struct iio_dev *indio_dev)
> {
> return NULL;
> -};
> +}
> #endif
>
> int iio_str_to_fixpoint(const char *str, int fract_mult, int *integer,
>
prev parent reply other threads:[~2013-08-31 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 23:15 [PATCH] iio: Remove trailing ; from function definitions Peter Meerwald
2013-08-31 18:16 ` 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=522232F0.2020503@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.