linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
Cc: "preid@electromag.com.au" <preid@electromag.com.au>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio:buffer: fix iio_dma_buffer_set_length() prototype mismatch
Date: Sun, 24 Jun 2018 14:52:17 +0100	[thread overview]
Message-ID: <20180624145217.131da6f2@archlinux> (raw)
In-Reply-To: <2126e135f7e414382131b4bbb8414d1eaac64f3a.camel@analog.com>

On Fri, 22 Jun 2018 09:32:52 +0000
"Ardelean, Alexandru" <alexandru.Ardelean@analog.com> wrote:

> On Fri, 2018-06-22 at 17:15 +0800, Phil Reid wrote:
> > On 22/06/2018 16:59, Alexandru Ardelean wrote: =20
> > > Fixes commit c043ec1ca5ba ("iio:buffer: make length types match kfifo
> > > types").
> > > When the length parameter's type was updated in the
> > > `iio_dma_buffer_set_length()` function, the prototype was omitted in
> > > the
> > > `include/linux/iio/buffer-dma.h` header.
> > >=20
> > > This causes a build error when running certain CFLAGS configurations
> > > that
> > > are a bit more pedantic. =20
> >=20
> > G'day Alexandru,
> >=20
> > I recently submitted a patch for the same issue.
> > see: https://patchwork.kernel.org/patch/10447649/
> >=20
> > Jonathan was holding of for a couple of weeks due to ordering issues.
> >  =20
>=20
> Sorry for the noise/duplication.
> I only looked into the iio/togreg tree and saw it wasn't there.
>=20
> Let's drop my patch.
>=20
> Thanks
> Alex

I've just applied Phil's patch and will try to send a pull request
out later today for that.

Thanks,

Jonathan

>=20
> >=20
> >  =20
> > >=20
> > > Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> > > ---
> > >   include/linux/iio/buffer-dma.h | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > >=20
> > > diff --git a/include/linux/iio/buffer-dma.h b/include/linux/iio/buffe=
r-
> > > dma.h
> > > index 767467d886de..67c75372b691 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);
> > >  =20
> > >   int iio_dma_buffer_init(struct iio_dma_buffer_queue *queue,
> > >  =20
> >=20
> > N_____r__y____b_X____v_^_)__{.n_+____{__*"__^n_r___z_=1A__h_____&__=1E_=
G___h_=03(_______j"__=1A_=1Bm______z______f___h___~_ =20


      reply	other threads:[~2018-06-24 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  8:59 [PATCH] iio:buffer: fix iio_dma_buffer_set_length() prototype mismatch Alexandru Ardelean
2018-06-22  9:15 ` Phil Reid
2018-06-22  9:32   ` Ardelean, Alexandru
2018-06-24 13:52     ` 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=20180624145217.131da6f2@archlinux \
    --to=jic23@kernel.org \
    --cc=alexandru.Ardelean@analog.com \
    --cc=linux-iio@vger.kernel.org \
    --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).