From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Van Hensbergen <ericvh@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>
Subject: linux-next: build failure after merge of the v9fs tree
Date: Tue, 22 Feb 2011 11:53:40 +1100 [thread overview]
Message-ID: <20110222115340.da48b908.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
Hi Eric,
After merging the v9fs tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "p9_payload_gup" [net/9p/9pnet_virtio.ko] undefined!
ERROR: "p9_nr_pages" [net/9p/9pnet_virtio.ko] undefined!
ERROR: "p9_release_req_pages" [net/9p/9pnet_virtio.ko] undefined!
Caused by commit ac8c81621fe5176f1bb18730e5db2e347af08255 ("[net/9p] Add
gup/zero_copy support to VirtIO transport layer").
I have used the v9fs tree from next-20110221 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-02-22 0:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 0:53 Stephen Rothwell [this message]
2011-02-22 5:20 ` linux-next: build failure after merge of the v9fs tree Venkateswararao Jujjuri (JV)
2011-02-22 5:30 ` Stephen Rothwell
2011-02-22 6:22 ` Venkateswararao Jujjuri (JV)
2011-02-22 14:57 ` Eric Van Hensbergen
2011-02-22 16:48 ` Venkateswararao Jujjuri (JV)
2011-12-01 1:02 Stephen Rothwell
2011-12-01 16:57 ` Joe Perches
2022-07-13 1:02 Stephen Rothwell
2022-07-13 1:06 ` Dominique Martinet
2022-12-05 4:03 Stephen Rothwell
2022-12-05 4:10 ` Dominique Martinet
2022-12-05 4:55 ` Stephen Rothwell
2022-12-05 14:31 ` Christian Schoenebeck
2022-12-05 20:40 ` Christian Schoenebeck
2022-12-05 22:41 ` Dominique Martinet
2022-12-08 15:55 ` Christian Schoenebeck
2022-12-08 23:53 ` Dominique Martinet
2022-12-09 14:40 ` Christian Schoenebeck
2022-12-09 21:24 ` Dominique Martinet
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=20110222115340.da48b908.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ericvh@gmail.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).