From: Jonathan Cameron <jic23@kernel.org>
To: Phil Reid <preid@electromag.com.au>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/1] iio: buffer: fix the function signature to match implementation
Date: Sun, 10 Jun 2018 14:35:16 +0100 [thread overview]
Message-ID: <20180610143516.66739628@archlinux> (raw)
In-Reply-To: <1528179310-10753-1-git-send-email-preid@electromag.com.au>
On Tue, 5 Jun 2018 14:15:10 +0800
Phil Reid <preid@electromag.com.au> wrote:
> linux/iio/buffer-dma.h was not updated to when length was changed to
> unsigned int.
>
> Fixes: c043ec1ca5ba ("iio:buffer: make length types match kfifo types")
> Signed-off-by: Phil Reid <preid@electromag.com.au>
Thanks, but I'll need to hold this for a few weeks due to some
ordering issues with some fixes that are queued up in my fixes branch
for after the merge window closes.
Give me a poke if I seem to have forgotten it in perhaps 2 weeks time.
Thanks,
Jonathan
> ---
> include/linux/iio/buffer-dma.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/iio/buffer-dma.h b/include/linux/iio/buffer-dma.h
> index 9182d4e..fbe053d 100644
> --- a/include/linux/iio/buffer-dma.h
> +++ b/include/linux/iio/buffer-dma.h
> @@ -141,7 +141,7 @@ int iio_dma_buffer_read(struct iio_buffer *buffer, size_t n,
> char __user *user_buffer);
> size_t iio_dma_buffer_data_available(struct iio_buffer *buffer);
> int iio_dma_buffer_set_bytes_per_datum(struct iio_buffer *buffer, size_t bpd);
> -int iio_dma_buffer_set_length(struct iio_buffer *buffer, int length);
> +int iio_dma_buffer_set_length(struct iio_buffer *buffer, unsigned int length);
> int iio_dma_buffer_request_update(struct iio_buffer *buffer);
>
> int iio_dma_buffer_init(struct iio_dma_buffer_queue *queue,
next prev parent reply other threads:[~2018-06-10 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 6:15 [PATCH 1/1] iio: buffer: fix the function signature to match implementation Phil Reid
2018-06-10 13:35 ` Jonathan Cameron [this message]
2018-06-24 13:24 ` Jonathan Cameron
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=20180610143516.66739628@archlinux \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=preid@electromag.com.au \
/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).