From: Joe Perches <joe@perches.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-ide <linux-ide@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/ata/sata_via.c - Eliminate "may be used uninitialized" warning
Date: Sun, 06 Apr 2008 15:00:07 -0700 [thread overview]
Message-ID: <1207519207.1803.60.camel@localhost> (raw)
In-Reply-To: <20080406215054.GI30987@cs181133002.pp.htv.fi>
On Mon, 2008-04-07 at 00:50 +0300, Adrian Bunk wrote:
> On Sun, Apr 06, 2008 at 02:45:20PM -0700, Joe Perches wrote:
> > Called by svia_init_one with a temporary,
> > so there's no effective code change.
> I'm not getting any warning here.
> Are you using an older gcc?
Yes. Slightly less than 4.3.0
$ gcc --version
gcc (GCC) 4.2.2 20071128 (prerelease) (4.2.2-3.1mdv2008.0)
$ git-show
commit 6fdf5e67fe8d3c83500dad9acae985132c2459a3
Merge: abd24df... e64a3cf...
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Fri Apr 4 15:09:44 2008 -0700
Merge branch 'upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/ralf/upstream-linus
* 'upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/ralf/upstream-linus:
[MIPS] Make KGDB compile on UP
[MIPS] Pb1200: Fix header breakage
$ make defconfig
[]
$ make clean
[]
$ make drivers/ata/sata_via.o
[]
CC drivers/ata/sata_via.o
drivers/ata/sata_via.c: In function ‘svia_init_one’:
drivers/ata/sata_via.c:504: warning: ‘host’ may be used uninitialized in this function
next prev parent reply other threads:[~2008-04-06 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 21:45 [PATCH] drivers/ata/sata_via.c - Eliminate "may be used uninitialized" warning Joe Perches
2008-04-06 21:50 ` Adrian Bunk
2008-04-06 22:00 ` Joe Perches [this message]
2008-04-07 7:53 ` Adrian Bunk
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=1207519207.1803.60.camel@localhost \
--to=joe@perches.com \
--cc=bunk@kernel.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.