From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: fix compilation warning about uninitialized var
Date: Thu, 31 Mar 2011 17:08:27 +0100 [thread overview]
Message-ID: <1301587707.2569.31.camel@dolmen> (raw)
In-Reply-To: <1301510786-28824-1-git-send-email-wfp5p@virginia.edu>
Hi,
Thanks for the patch, but it is already fixed in my -nmw tree,
Steve.
On Wed, 2011-03-30 at 14:46 -0400, Bill Pemberton wrote:
> fix the following warning:
>
> fs/gfs2/inode.c:188:16: warning: ?inode? may be used uninitialized in this function
>
> The warning is bogus as inode is not used in this function
> uninitialized.
>
> Signed-off-by: Bill Pemberton <wfp5p@virginia.edu>
> ---
> fs/gfs2/inode.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/gfs2/inode.c b/fs/gfs2/inode.c
> index 97d54a2..b888099 100644
> --- a/fs/gfs2/inode.c
> +++ b/fs/gfs2/inode.c
> @@ -185,7 +185,7 @@ struct inode *gfs2_lookup_by_inum(struct gfs2_sbd *sdp, u64 no_addr,
> {
> struct super_block *sb = sdp->sd_vfs;
> struct gfs2_holder i_gh;
> - struct inode *inode;
> + struct inode *uninitialized_var(inode);
> int error;
>
> error = gfs2_glock_nq_num(sdp, no_addr, &gfs2_inode_glops,
parent reply other threads:[~2011-03-31 16:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1301510786-28824-1-git-send-email-wfp5p@virginia.edu>]
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=1301587707.2569.31.camel@dolmen \
--to=swhiteho@redhat.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