From: "Thomas Weißschuh" <linux@weissschuh.net>
To: v9fs-developer@lists.sourceforge.net, netdev@vger.kernel.org
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"Dominique Martinet" <asmadeus@codewreck.org>,
"Eric Van Hensbergen" <ericvh@gmail.com>,
"Latchesar Ionkov" <lucho@ionkov.net>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Stefano Stabellini" <stefano@aporeto.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/4] 9p/xen: autoload when xenbus service is available
Date: Wed, 3 Nov 2021 20:38:22 +0100 [thread overview]
Message-ID: <20211103193823.111007-4-linux@weissschuh.net> (raw)
In-Reply-To: <20211103193823.111007-1-linux@weissschuh.net>
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
net/9p/trans_xen.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/9p/trans_xen.c b/net/9p/trans_xen.c
index e264dcee019a..9c4c565f92e4 100644
--- a/net/9p/trans_xen.c
+++ b/net/9p/trans_xen.c
@@ -561,6 +561,7 @@ static void p9_trans_xen_exit(void)
}
module_exit(p9_trans_xen_exit);
+MODULE_ALIAS("xen:9pfs");
MODULE_AUTHOR("Stefano Stabellini <stefano@aporeto.com>");
MODULE_DESCRIPTION("Xen Transport for 9P");
MODULE_LICENSE("GPL");
--
2.33.1
next prev parent reply other threads:[~2021-11-03 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 19:38 [PATCH v2 0/4] net/9p: optimize transport module loading Thomas Weißschuh
2021-11-03 19:38 ` [PATCH v2 1/4] net/9p: autoload transport modules Thomas Weißschuh
2021-11-03 19:38 ` [PATCH v2 2/4] 9p/trans_fd: split into dedicated module Thomas Weißschuh
2022-01-10 0:57 ` Dominique Martinet
2022-01-10 6:42 ` Thomas Weißschuh
2021-11-03 19:38 ` Thomas Weißschuh [this message]
2021-11-03 19:38 ` [PATCH v2 4/4] net/p9: load default transports Thomas Weißschuh
2021-11-08 18:50 ` Thomas Weißschuh
2021-11-08 22:31 ` 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=20211103193823.111007-4-linux@weissschuh.net \
--to=linux@weissschuh.net \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=stefano@aporeto.com \
--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 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).