From: Arnd Bergmann <arnd@arndb.de>
To: Juergen Gross <jgross@suse.com>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
Stefano Stabellini <sstabellini@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Eric Van Hensbergen <ericvh@gmail.com>,
netdev@vger.kernel.org, groug@kaod.org,
linux-kernel@vger.kernel.org,
Stefano Stabellini <stefano@aporeto.com>,
v9fs-developer@lists.sourceforge.net,
Ron Minnich <rminnich@sandia.gov>,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
"David S. Miller" <davem@davemloft.net>
Subject: [PATCH] xen/9pfs: select CONFIG_XEN_XENBUS_FRONTEND
Date: Wed, 19 Apr 2017 19:06:39 +0200 [thread overview]
Message-ID: <20170419170648.3041204-1-arnd@arndb.de> (raw)
All Xen frontends need to select this symbol to avoid a link error:
net/built-in.o: In function `p9_trans_xen_init':
:(.text+0x149e9c): undefined reference to `__xenbus_register_frontend'
Fixes: d4b40a02f837 ("xen/9pfs: build 9pfs Xen transport driver")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
net/9p/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/9p/Kconfig b/net/9p/Kconfig
index 3f286f1bd1d3..e6014e0e51f7 100644
--- a/net/9p/Kconfig
+++ b/net/9p/Kconfig
@@ -24,6 +24,7 @@ config NET_9P_VIRTIO
config NET_9P_XEN
depends on XEN
+ select XEN_XENBUS_FRONTEND
tristate "9P Xen Transport"
help
This builds support for a transport for 9pfs between
--
2.9.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-04-19 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 17:06 Arnd Bergmann [this message]
2017-04-19 17:21 ` [PATCH] xen/9pfs: select CONFIG_XEN_XENBUS_FRONTEND Stefano Stabellini
2017-04-19 23:10 ` Stefano Stabellini
2017-04-20 3:54 ` Juergen Gross
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=20170419170648.3041204-1-arnd@arndb.de \
--to=arnd@arndb.de \
--cc=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=groug@kaod.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=rminnich@sandia.gov \
--cc=sstabellini@kernel.org \
--cc=stefano@aporeto.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=xen-devel@lists.xenproject.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