From: David Howells <dhowells@redhat.com>
To: torvalds@osdl.org, akpm@linux-foundation.com
Cc: dhowells@redhat.com, Kyle McMartin <kyle@redhat.com>,
Xiaotian Feng <dfeng@redhat.com>,
Stefan Lippers-Hollmann <s.l-h@gmx.de>,
linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net, ericvh@gmail.com
Subject: [PATCH] 9p: fix build breakage introduced by 201a15428bd54f83eccec8b7c64a04b8f9431204
Date: Tue, 01 Dec 2009 13:38:45 +0000 [thread overview]
Message-ID: <25412.1259674725@redhat.com> (raw)
While building 2.6.32-rc8-git2 for Fedora I noticed the following thinko in
commit 201a15428bd54f83eccec8b7c64a04b8f9431204:
fs/9p/cache.c: In function '__v9fs_fscache_release_page':
fs/9p/cache.c:346: error: 'vnode' undeclared (first use in this function)
fs/9p/cache.c:346: error: (Each undeclared identifier is reported only once
fs/9p/cache.c:346: error: for each function it appears in.)
make[2]: *** [fs/9p/cache.o] Error 1
Fix the 9P filesystem to correctly construct the argument to
fscache_maybe_release_page().
Signed-off-by: Kyle McMartin <kyle@redhat.com>
Signed-off-by: Xiaotian Feng <dfeng@redhat.com> [from identical patch]
Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [from identical patch]
Signed-off-by: David Howells <dhowells@redhat.com>
---
fs/9p/cache.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/9p/cache.c b/fs/9p/cache.c
index bcc5357..e777961 100644
--- a/fs/9p/cache.c
+++ b/fs/9p/cache.c
@@ -343,7 +343,7 @@ int __v9fs_fscache_release_page(struct page *page, gfp_t gfp)
BUG_ON(!vcookie->fscache);
- return fscache_maybe_release_page(vnode->cache, page, gfp);
+ return fscache_maybe_release_page(vcookie->fscache, page, gfp);
}
void __v9fs_fscache_invalidate_page(struct page *page)
next reply other threads:[~2009-12-01 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 13:38 David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-01 6:56 [PATCH] 9p: fix build breakage introduced by 201a15428bd54f83eccec8b7c64a04b8f9431204 Kyle McMartin
2009-12-01 10:50 ` David Howells
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=25412.1259674725@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.com \
--cc=dfeng@redhat.com \
--cc=ericvh@gmail.com \
--cc=kyle@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.l-h@gmx.de \
--cc=torvalds@osdl.org \
--cc=v9fs-developer@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 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.