From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [PATCH 0/2] Fix a few more warnings
Date: Mon, 29 Oct 2012 09:38:09 -0200 [thread overview]
Message-ID: <20121029093809.0e61d769@redhat.com> (raw)
In-Reply-To: <6407737.rOrJiiUORE@avalon>
Em Mon, 29 Oct 2012 11:38:39 +0100
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> Hi Mauro,
>
> On Monday 29 October 2012 08:21:56 Mauro Carvalho Chehab wrote:
> > Hans Verkuil yesterday's build still got two warnings at the
> > generic drivers:
> > http://hverkuil.home.xs4all.nl/logs/Sunday.log
> >
> > They didn't appear at i386 build probably because of some
> > optimization done there.
> >
> > Anyway, fixing them are trivial, so let's do it.
> >
> > After applying those patches, the only drivers left producing
> > warnings are the following platform drivers:
> >
> > drivers/media/platform/davinci/dm355_ccdc.c
> > drivers/media/platform/davinci/dm644x_ccdc.c
> > drivers/media/platform/davinci/vpbe_osd.c
> > drivers/media/platform/omap3isp/ispccdc.c
> > drivers/media/platform/omap3isp/isph3a_aewb.c
> > drivers/media/platform/omap3isp/isph3a_af.c
> > drivers/media/platform/omap3isp/isphist.c
> > drivers/media/platform/omap3isp/ispqueue.c
> > drivers/media/platform/omap3isp/ispvideo.c
> > drivers/media/platform/omap/omap_vout.c
> > drivers/media/platform/s5p-fimc/fimc-capture.c
> > drivers/media/platform/s5p-fimc/fimc-lite.c
> > drivers/media/platform/sh_vou.c
> > drivers/media/platform/soc_camera/sh_mobile_ceu_camera.c
> >
> > Platform driver maintainers: please fix, as those warnings could be
> > hiding real bugs.
>
> I've sent you a pull request for v3.7 on Thu, 25 Oct 2012 with two patches
> that fix most of the warnings:
>
> omap3isp: video: Fix warning caused by bad vidioc_s_crop prototype
> omap3isp: Fix warning caused by bad subdev events operations prototypes
Ok. I'll review it today.
> The other two OMAP3 ISP warnings are false positive. They will go away when
> we'll switch to videobuf2 (which is on my to-do list).
While you're not ready to submit the omap3 vb2 patches, would you mind fixing
them? Failing to do that will prevent us to improve the process of detecting
warnings at day zero. For example, I suspect that Hans automatic compilation
tool will keep saying that WARNINGS are present at -git, while we don't fix
all those platform warnings.
Regards,
Mauro
prev parent reply other threads:[~2012-10-29 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1351506118-2385-1-git-send-email-mchehab@redhat.com>
2012-10-29 11:19 ` [PATCH 0/2] Fix a few more warnings Sylwester Nawrocki
2012-10-29 11:28 ` Ezequiel Garcia
2012-10-29 11:32 ` Mauro Carvalho Chehab
2012-10-29 11:38 ` Ezequiel Garcia
2012-10-29 14:12 ` Sylwester Nawrocki
2012-10-29 14:53 ` Mauro Carvalho Chehab
[not found] ` <6407737.rOrJiiUORE@avalon>
2012-10-29 11:38 ` Mauro Carvalho Chehab [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=20121029093809.0e61d769@redhat.com \
--to=mchehab@redhat.com \
--cc=g.liakhovetski@gmx.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=s.nawrocki@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;
as well as URLs for NNTP newsgroup(s).