linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jim Davis <jim.epost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
	linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: randconfig build error with next-20131125, in drivers/iio/light
Date: Mon, 25 Nov 2013 17:13:09 +0000	[thread overview]
Message-ID: <1bbe329e-a128-4d08-b79c-d9285dbf4aae@email.android.com> (raw)
In-Reply-To: <CA+r1ZhinxJBB3dgCKxoMXV0ioVR0jrS7ha=SY-qT212AvDSkVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Thanks for the report. We have a fix queued up. I have just been a bit lax sending the pull request. Note I believe the issue is in Linus' tree as well.

Thanks again

Jonathan

Jim Davis <jim.epost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>Building with the attached random configuration file,
>
>drivers/iio/light/tcs3472.c: In function ‘tcs3472_trigger_handler’:
>drivers/iio/light/tcs3472.c:195:2: error: implicit declaration of
>function ‘iio_push_to_buffers_with_timestamp’
>[-Werror=implicit-function-declaration]
>  iio_push_to_buffers_with_timestamp(indio_dev, data->buffer,
>  ^
>cc1: some warnings being treated as errors
>make[3]: *** [drivers/iio/light/tcs3472.o] Error 1

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

      parent reply	other threads:[~2013-11-25 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 17:04 randconfig build error with next-20131125, in drivers/iio/light Jim Davis
     [not found] ` <CA+r1ZhinxJBB3dgCKxoMXV0ioVR0jrS7ha=SY-qT212AvDSkVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-25 17:13   ` Borislav Petkov
2013-11-25 17:13   ` 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=1bbe329e-a128-4d08-b79c-d9285dbf4aae@email.android.com \
    --to=jic23-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=jim.epost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org \
    /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).