public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org,
	LKML <linux-kernel@vger.kernel.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] i915, debugfs: Fix uninitialized warning
Date: Fri, 22 Nov 2013 17:09:59 +0200	[thread overview]
Message-ID: <20131122150959.GD10036@intel.com> (raw)
In-Reply-To: <20131121162535.GK26009@pd.tnic>

On Thu, Nov 21, 2013 at 05:25:35PM +0100, Borislav Petkov wrote:
> On Thu, Nov 21, 2013 at 05:10:30PM +0100, Richard Weinberger wrote:
> > > diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> > > index 6ed45a984230..1191aa47adc9 100644
> > > --- a/drivers/gpu/drm/i915/i915_debugfs.c
> > > +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> > > @@ -2347,7 +2347,7 @@ static int pipe_crc_set_source(struct drm_device *dev, enum pipe pipe,
> > >  {
> > >         struct drm_i915_private *dev_priv = dev->dev_private;
> > >         struct intel_pipe_crc *pipe_crc = &dev_priv->pipe_crc[pipe];
> > > -       u32 val;
> > > +       u32 val = 0; /* shut up gcc */
> > 
> > Wouldn't it be better to use uninitialized_var() here?
> 
> I remember Linus' rant about this macro so that's why I don't use it
> anymore.
> 
> In this specific case, it doesn't matter whichever we do so I'll let the
> maintainer make a wish :)

IIRC this warning was there for me too on gcc 4.6, but it disappeared
on gcc 4.7, which is why I decided not to send a patch for it.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2013-11-22 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 15:49 [PATCH] i915, debugfs: Fix uninitialized warning Borislav Petkov
2013-11-21 16:10 ` Richard Weinberger
2013-11-21 16:25   ` Borislav Petkov
2013-11-22 15:09     ` Ville Syrjälä [this message]
2013-11-23 13:51       ` Borislav Petkov
2013-11-21 20:58 ` Daniel Vetter

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=20131122150959.GD10036@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.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