Linux Media Controller development
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Laurent Pinchart <laurent.pinchart@skynet.be>
Cc: Alexey Klimov <klimov.linux@gmail.com>,
	linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [patch review] uvc_driver: fix compile warning
Date: Mon, 20 Apr 2009 14:50:31 -0300	[thread overview]
Message-ID: <20090420145031.2ffd860a@pedra.chehab.org> (raw)
In-Reply-To: <200904201925.00656.laurent.pinchart@skynet.be>

On Mon, 20 Apr 2009 19:25:00 +0200
Laurent Pinchart <laurent.pinchart@skynet.be> wrote:

> Hi Alexey,
> 
> On Sunday 19 April 2009 22:03:09 Alexey Klimov wrote:
> > Hello, all
> > I saw warnings in v4l-dvb daily build.
> > May this patch be helpful?
> 
> I can't reproduce the problem with gcc 4.3.2.
> 
> Hans, what's the policy for fixing gcc-related issues ? Should the code use 
> uninitialized_var() to make every gcc version happy, or can ignore the 
> warnings when a newer gcc version fixes the problem 

Laurent,

The kernel way is to use unitialized_var() on such cases.

Personally, I don't like very much this approach, since it will get rid forever
of such error for that var. However, a future patch could make that var truly
uninitialized. So, an extra care should be taken on every patch touching a var
that uses uninitialized_var() macro.

>From my side, I accept patches with both ways to fix it.

Cheers,
Mauro

  reply	other threads:[~2009-04-20 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 20:03 [patch review] uvc_driver: fix compile warning Alexey Klimov
2009-04-20 17:25 ` Laurent Pinchart
2009-04-20 17:50   ` Mauro Carvalho Chehab [this message]
2009-04-20 20:12     ` Laurent Pinchart
2009-04-20 20:47       ` Mauro Carvalho Chehab

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=20090420145031.2ffd860a@pedra.chehab.org \
    --to=mchehab@infradead.org \
    --cc=hverkuil@xs4all.nl \
    --cc=klimov.linux@gmail.com \
    --cc=laurent.pinchart@skynet.be \
    --cc=linux-media@vger.kernel.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