From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: V4.1-RC build error after commit 77a3c6f
Date: Mon, 13 Jul 2015 11:25:35 +0300 [thread overview]
Message-ID: <3803143.Bo2k5SCl7G@avalon> (raw)
In-Reply-To: <55A315E4.7090601@lwfinger.net>
Hi Larry,
On Sunday 12 July 2015 20:35:32 Larry Finger wrote:
> On 07/12/2015 06:10 PM, Laurent Pinchart wrote:
> > Hi Larry,
> >
> > Thank you for the report.
> >
> > On Saturday 11 July 2015 16:27:36 Larry Finger wrote:
> >> Beginning with the commit in the subject, I get the following build
error:
> >> CC [M] drivers/media/v4l2-core/videobuf2-core.o
> >>
> >> 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();
> >> ^
> >>
> >> cc1: some warnings being treated as errors
> >>
> >> My .config is attached.
> >
> > Indeed, __WARN isn't defined when CONFIG_BUG isn't set. My bad :-/
> >
> > I've send a patch to fix this (you've been CC'ed), could you please review
> > it ?
> >
> > And I've just noticed that I forgot to add your Reported-by: tag, please
> > feel free to add it to the review.
>
> I added my "Acked-by:" for the __WARN to WARN_ON part. In addition, the rest
> looks good.
Thank you.
> I do not need a Reported-by to be added. I'm a volunteer, thus it does not
> matter how many times my name is mentioned. Another one will never increase
> my remuneration.
I'm afraid I wouldn't be in a position to increase your remuneration even if
you were paid to report issues :-) Still, the point of the Reported-by: tag is
recognition of contributors. This topic is currently being discussed as a
canditate for the Linux kernel summit (see
http://lists.linuxfoundation.org/pipermail/ksummit-discuss/2015-July/001318.html for instance). Feel free to chime in, we mostly have long
time kernel maintainers in the e-mail thread, it would be nice to get the
point of few of volunteers as well.
> I have also submitted a patch to make certain that __WARN is defined even
> when CONFIG_DEBUG is not defined. It may not be accepted, but if it does,
> no one else will be caught this way.
Thank you.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2015-07-13 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 21:27 V4.1-RC build error after commit 77a3c6f Larry Finger
2015-07-11 21:30 ` Larry Finger
2015-07-12 23:10 ` Laurent Pinchart
2015-07-13 1:35 ` Larry Finger
2015-07-13 8:25 ` Laurent Pinchart [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=3803143.Bo2k5SCl7G@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
/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