From: Randy Dunlap <rdunlap@infradead.org>
To: Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
pawel@osciak.com, Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
mchehab@osg.samsung.com,
linux-media <linux-media@vger.kernel.org>
Subject: Re: randconfig build error with next-20150620, in drivers/media/v4l2-core/videobuf2-core.c
Date: Wed, 01 Jul 2015 11:07:08 -0700 [thread overview]
Message-ID: <55942C4C.70209@infradead.org> (raw)
In-Reply-To: <CA+r1Zhheo-_o_AJ2sji6FPKNLiHYmjP81__saW7Jv63wMex9BQ@mail.gmail.com>
On 06/20/15 09:44, Jim Davis wrote:
> Building with the attached random configuration file,
>
> drivers/media/v4l2-core/videobuf2-core.c: In function ‘vb2_warn_zero_bytesused’:
> drivers/media/v4l2-core/videobuf2-core.c:1253:2: error: implicit declaration of
> function ‘__WARN’ [-Werror=implicit-function-declaration]
> __WARN();
> ^
>
When CONFIG_BUG is not enabled, there is no definition of __WARN().
Should be add an empty stub for __WARN() or just change the only
user (caller) of it to do something different?
--
~Randy
prev parent reply other threads:[~2015-07-01 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 16:44 randconfig build error with next-20150620, in drivers/media/v4l2-core/videobuf2-core.c Jim Davis
2015-07-01 18:07 ` Randy Dunlap [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=55942C4C.70209@infradead.org \
--to=rdunlap@infradead.org \
--cc=jim.epost@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@osg.samsung.com \
--cc=pawel@osciak.com \
--cc=sfr@canb.auug.org.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