From: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
To: Jim Davis <jim.epost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jic23-DgEjT+Ai2ygdnm+yROfE0A@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 18:13:01 +0100 [thread overview]
Message-ID: <20131125171301.GB11463@pd.tnic> (raw)
In-Reply-To: <CA+r1ZhinxJBB3dgCKxoMXV0ioVR0jrS7ha=SY-qT212AvDSkVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Nov 25, 2013 at 10:04:44AM -0700, Jim Davis 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
Feel like giving it a try to write a fix for it? It seems to me
tcs3472.c should depend on IIO_BUFFER... :-)
HTH.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev 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 [this message]
2013-11-25 17:13 ` 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=20131125171301.GB11463@pd.tnic \
--to=bp-gina5biwoiwzqb+pc5nmwq@public.gmane.org \
--cc=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).