All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: Jim Rees <rees@umich.edu>
Cc: Benny Halevy <bhalevy@tonian.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Silence compiler warning
Date: Tue, 18 Oct 2011 13:50:41 +0400	[thread overview]
Message-ID: <4E9D4BF1.9070401@parallels.com> (raw)
In-Reply-To: <1318810012-15140-1-git-send-email-rees@umich.edu>

I have this warning also:
fs/nfs/callback_proc.c:116: warning: ‘ino’ may be used uninitialized in this 
function

17.10.2011 04:06, Jim Rees пишет:
> fs/nfs/callback_proc.c: In function ‘do_callback_layoutrecall’:
> fs/nfs/callback_proc.c:115:26: warning: ‘lo’ may be used uninitialized in this function
>
> No functional change. If no layout is found, we'll return before  using
> "lo".
>
> Signed-off-by: Jim Rees<rees@umich.edu>
> ---
>   fs/nfs/callback_proc.c |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/nfs/callback_proc.c b/fs/nfs/callback_proc.c
> index 43926ad..93633f1 100644
> --- a/fs/nfs/callback_proc.c
> +++ b/fs/nfs/callback_proc.c
> @@ -112,7 +112,7 @@ static u32 initiate_file_draining(struct nfs_client *clp,
>   				  struct cb_layoutrecallargs *args)
>   {
>   	struct nfs_server *server;
> -	struct pnfs_layout_hdr *lo;
> +	struct pnfs_layout_hdr *lo = NULL;
>   	struct inode *ino;
>   	bool found = false;
>   	u32 rv = NFS4ERR_NOMATCHING_LAYOUT;


-- 
Best regards,
Stanislav Kinsbursky

  parent reply	other threads:[~2011-10-18  9:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17  0:06 [PATCH] Silence compiler warning Jim Rees
2011-10-17  1:57 ` Benny Halevy
2011-10-17  2:36   ` Jim Rees
2011-10-18  9:50 ` Stanislav Kinsbursky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-18 13:07 Benny Halevy
2011-11-01  1:37 Jim Rees
2011-11-01  2:30 ` Trond Myklebust
2011-11-01  2:42   ` Jim Rees
2011-11-01  2:56     ` Trond Myklebust
2011-11-01  3:01       ` Jim Rees

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=4E9D4BF1.9070401@parallels.com \
    --to=skinsbursky@parallels.com \
    --cc=bhalevy@tonian.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.edu \
    /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.