From: William Lee Irwin III <wli@holomorphy.com>
To: nfs@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: fix nfs_writeback_done() warning
Date: Fri, 17 Jan 2003 01:15:03 -0800 [thread overview]
Message-ID: <20030117091503.GE940@holomorphy.com> (raw)
I get complaints about an unused variable "inode". This removes
the variable and open-codes the dereference to data->inode, hence
fixing the warning.
diff -urpN mm1-2.5.59/fs/nfs/write.c numaq-2.5.59/fs/nfs/write.c
--- mm1-2.5.59/fs/nfs/write.c 2003-01-16 18:22:26.000000000 -0800
+++ numaq-2.5.59/fs/nfs/write.c 2003-01-17 01:12:29.000000000 -0800
@@ -829,7 +829,6 @@ nfs_writeback_done(struct rpc_task *task
struct nfs_write_data *data = (struct nfs_write_data *) task->tk_calldata;
struct nfs_writeargs *argp = &data->args;
struct nfs_writeres *resp = &data->res;
- struct inode *inode = data->inode;
struct nfs_page *req;
struct page *page;
@@ -863,7 +862,7 @@ nfs_writeback_done(struct rpc_task *task
if (time_before(complain, jiffies)) {
dprintk("NFS: faulty NFS server %s:"
" (committed = %d) != (stable = %d)\n",
- NFS_SERVER(inode)->hostname,
+ NFS_SERVER(data->inode)->hostname,
data->verf.committed, argp->stable);
complain = jiffies + 300 * HZ;
}
reply other threads:[~2003-01-17 9:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030117091503.GE940@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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