From: Jonathan Cameron <jic23@kernel.org>
To: Cristina Opriceana <cristina.opriceana@gmail.com>
Cc: daniel.baluta@intel.com, octavian.purdila@intel.com,
lars@metafoo.de, pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: Fix parameters in iio_triggered_buffer_setup
Date: Sun, 05 Jul 2015 15:20:25 +0100 [thread overview]
Message-ID: <55993D29.4080509@kernel.org> (raw)
In-Reply-To: <ad6b8f39a9861d58cbf4c753d1499675e1500bef.1435065212.git.cristina.opriceana@gmail.com>
On 23/06/15 14:34, Cristina Opriceana wrote:
> This patch renames the top half handler and the bottom half handler
> of iio_triggered_buffer_setup() in accordance with their usage.
> The bottom half has been renamed to reflect the fact that it is a
> thread based call, compliant with iio_alloc_pollfunc().
> The names of the parameters were swapped, thus creating confusion.
>
> Signed-off-by: Cristina Opriceana <cristina.opriceana@gmail.com>
Applied.
Thanks,
Jonathan
> ---
> Changes in v2:
> - rename params in iio_triggered_buffer_setup() to h and thread
> - make the commit message reflect the changes
> drivers/iio/industrialio-triggered-buffer.c | 12 ++++++------
> include/linux/iio/triggered_buffer.h | 4 ++--
> 2 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/iio/industrialio-triggered-buffer.c b/drivers/iio/industrialio-triggered-buffer.c
> index 15a5341..4b2858b 100644
> --- a/drivers/iio/industrialio-triggered-buffer.c
> +++ b/drivers/iio/industrialio-triggered-buffer.c
> @@ -24,8 +24,8 @@ static const struct iio_buffer_setup_ops iio_triggered_buffer_setup_ops = {
> /**
> * iio_triggered_buffer_setup() - Setup triggered buffer and pollfunc
> * @indio_dev: IIO device structure
> - * @pollfunc_bh: Function which will be used as pollfunc bottom half
> - * @pollfunc_th: Function which will be used as pollfunc top half
> + * @h: Function which will be used as pollfunc top half
> + * @thread: Function which will be used as pollfunc bottom half
> * @setup_ops: Buffer setup functions to use for this device.
> * If NULL the default setup functions for triggered
> * buffers will be used.
> @@ -42,8 +42,8 @@ static const struct iio_buffer_setup_ops iio_triggered_buffer_setup_ops = {
> * iio_triggered_buffer_cleanup().
> */
> int iio_triggered_buffer_setup(struct iio_dev *indio_dev,
> - irqreturn_t (*pollfunc_bh)(int irq, void *p),
> - irqreturn_t (*pollfunc_th)(int irq, void *p),
> + irqreturn_t (*h)(int irq, void *p),
> + irqreturn_t (*thread)(int irq, void *p),
> const struct iio_buffer_setup_ops *setup_ops)
> {
> struct iio_buffer *buffer;
> @@ -57,8 +57,8 @@ int iio_triggered_buffer_setup(struct iio_dev *indio_dev,
>
> iio_device_attach_buffer(indio_dev, buffer);
>
> - indio_dev->pollfunc = iio_alloc_pollfunc(pollfunc_bh,
> - pollfunc_th,
> + indio_dev->pollfunc = iio_alloc_pollfunc(h,
> + thread,
> IRQF_ONESHOT,
> indio_dev,
> "%s_consumer%d",
> diff --git a/include/linux/iio/triggered_buffer.h b/include/linux/iio/triggered_buffer.h
> index c378ebe..f72f70d 100644
> --- a/include/linux/iio/triggered_buffer.h
> +++ b/include/linux/iio/triggered_buffer.h
> @@ -7,8 +7,8 @@ struct iio_dev;
> struct iio_buffer_setup_ops;
>
> int iio_triggered_buffer_setup(struct iio_dev *indio_dev,
> - irqreturn_t (*pollfunc_bh)(int irq, void *p),
> - irqreturn_t (*pollfunc_th)(int irq, void *p),
> + irqreturn_t (*h)(int irq, void *p),
> + irqreturn_t (*thread)(int irq, void *p),
> const struct iio_buffer_setup_ops *setup_ops);
> void iio_triggered_buffer_cleanup(struct iio_dev *indio_dev);
>
>
prev parent reply other threads:[~2015-07-05 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 13:34 [PATCH v2] iio: Fix parameters in iio_triggered_buffer_setup Cristina Opriceana
2015-07-05 14:20 ` 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=55993D29.4080509@kernel.org \
--to=jic23@kernel.org \
--cc=cristina.opriceana@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--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 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).