From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org
Subject: Re: [PATCH 1/2] media: ipu3: shut up warnings produced with W=1
Date: Tue, 19 Feb 2019 11:27:19 -0300 [thread overview]
Message-ID: <20190219112719.6275a8ce@coco.lan> (raw)
In-Reply-To: <20190219140317.hmsyybhbe7lan2ek@kekkonen.localdomain>
Em Tue, 19 Feb 2019 16:03:17 +0200
Sakari Ailus <sakari.ailus@linux.intel.com> escreveu:
> Hi Mauro,
>
> On Tue, Feb 19, 2019 at 09:00:29AM -0500, Mauro Carvalho Chehab wrote:
> > There are lots of warnings produced by this driver. It is not
> > as much as atomisp, but it is still a lot.
> >
> > So, use the same solution to hide most of them.
> > Those need to be fixed before promoting it out of staging,
> > so add it at the TODO list.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > ---
> > drivers/staging/media/ipu3/Makefile | 6 ++++++
> > drivers/staging/media/ipu3/TODO | 2 ++
> > 2 files changed, 8 insertions(+)
> >
> > diff --git a/drivers/staging/media/ipu3/Makefile b/drivers/staging/media/ipu3/Makefile
> > index fb146d178bd4..fa7fa3372bcb 100644
> > --- a/drivers/staging/media/ipu3/Makefile
> > +++ b/drivers/staging/media/ipu3/Makefile
> > @@ -9,3 +9,9 @@ ipu3-imgu-objs += \
> > ipu3-css.o ipu3-v4l2.o ipu3.o
> >
> > obj-$(CONFIG_VIDEO_IPU3_IMGU) += ipu3-imgu.o
> > +
> > +# HACK! While this driver is in bad shape, don't enable several warnings
> > +# that would be otherwise enabled with W=1
> > +ccflags-y += $(call cc-disable-warning, packed-not-aligned)
> > +ccflags-y += $(call cc-disable-warning, type-limits)
> > +ccflags-y += $(call cc-disable-warning, unused-const-variable)
>
> I'm preparing patches to address these. Could you wait a little bit more,
> please?
Those warnings are there for a while...
It has been really painful for my workflow all those ipu3
warnings, as they're preventing seeing troubles on other places.
Anyway, as soon as you address the issues, we can (partially
or fully) revert those changes.
Thanks,
Mauro
prev parent reply other threads:[~2019-02-19 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 14:00 [PATCH 1/2] media: ipu3: shut up warnings produced with W=1 Mauro Carvalho Chehab
2019-02-19 14:00 ` [PATCH 2/2] ipu3-mmu: fix some kernel-doc macros Mauro Carvalho Chehab
2019-02-19 14:03 ` Sakari Ailus
2019-02-19 14:03 ` [PATCH 1/2] media: ipu3: shut up warnings produced with W=1 Sakari Ailus
2019-02-19 14:27 ` 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=20190219112719.6275a8ce@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sakari.ailus@linux.intel.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