linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: zippel@linux-m68k.org, linux-fsdevel@vger.kernel.org,
	rusty@rustcorp.com.au, linux-audit@redhat.com
Subject: [PATCH 6/6]afs:fsclient.c Fix variable 'bp' set but not used
Date: Fri, 11 Jun 2010 13:41:09 -0700	[thread overview]
Message-ID: <1276288869-16815-7-git-send-email-justinmattock@gmail.com> (raw)
In-Reply-To: <1276288869-16815-1-git-send-email-justinmattock@gmail.com>

This fixes this warning message I'm getting:

  CC [M]  fs/afs/fsclient.o
fs/afs/fsclient.c: In function 'afs_deliver_fs_xxxx_lock':
fs/afs/fsclient.c:1759:16: warning: variable 'bp' set but not used
  CC [M]  fs/afs/inode.o

 Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>

---
 fs/afs/fsclient.c |    5 +----
 1 files changed, 1 insertions(+), 4 deletions(-)

diff --git a/fs/afs/fsclient.c b/fs/afs/fsclient.c
index 4bd0218..aca2ccb 100644
--- a/fs/afs/fsclient.c
+++ b/fs/afs/fsclient.c
@@ -1756,8 +1756,7 @@ int afs_fs_get_volume_status(struct afs_server *server,
 static int afs_deliver_fs_xxxx_lock(struct afs_call *call,
 				    struct sk_buff *skb, bool last)
 {
-	const __be32 *bp;
-
+	
 	_enter("{%u},{%u},%d", call->unmarshall, skb->len, last);
 
 	afs_transfer_reply(call, skb);
@@ -1767,8 +1766,6 @@ static int afs_deliver_fs_xxxx_lock(struct afs_call *call,
 	if (call->reply_size != call->reply_max)
 		return -EBADMSG;
 
-	/* unmarshall the reply once we've received all of it */
-	bp = call->buffer;
 	/* xdr_decode_AFSVolSync(&bp, call->replyX); */
 
 	_leave(" = 0 [done]");
-- 
1.7.1.rc1.21.gf3bd6

      parent reply	other threads:[~2010-06-11 20:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 20:41 [PATCH 0/6] Fix gcc warnings of unused variables etc Justin P. Mattock
2010-06-11 20:41 ` [PATCH 1/6]scripts:conf.c Fix warning: variable 'type' set but not used Justin P. Mattock
2010-06-11 22:19   ` Michal Marek
2010-06-11 22:24     ` Justin P. Mattock
2010-06-11 20:41 ` [PATCH 2/6]kernel:audit.c Fix warning: variable 'nlh' " Justin P. Mattock
2010-06-11 21:14   ` Geert Uytterhoeven
2010-06-11 22:03     ` Justin P. Mattock
2010-06-19  4:45     ` Justin P. Mattock
2010-06-19  8:06       ` Geert Uytterhoeven
2010-06-19 13:29         ` Justin P. Mattock
2010-06-11 20:41 ` [PATCH 3/6]cifs Fix variable not set warnings Justin P. Mattock
2010-06-20 13:22   ` Alessandro Guido
2010-06-20 13:29     ` Justin P. Mattock
2010-06-11 20:41 ` [PATCH 4/6]hfs Fix variable set but not used Justin P. Mattock
2010-06-11 20:41 ` [PATCH 5/6]kernel:module.c variable 'nowarn' " Justin P. Mattock
2010-06-11 21:17   ` Geert Uytterhoeven
2010-06-11 22:06     ` Justin P. Mattock
2010-06-19  5:04     ` Justin P. Mattock
2010-06-19  8:08       ` Geert Uytterhoeven
2010-06-19 13:41         ` Justin P. Mattock
2010-06-19 19:10         ` Justin P. Mattock
2010-06-19 19:45           ` Geert Uytterhoeven
2010-06-19 20:10             ` Justin P. Mattock
2010-06-19 20:23               ` Geert Uytterhoeven
2010-06-19 20:26                 ` Justin P. Mattock
2010-06-11 20:41 ` Justin P. Mattock [this message]

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=1276288869-16815-7-git-send-email-justinmattock@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).