From: Dominique Martinet <asmadeus@codewreck.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
v9fs-developer@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/9p: autoload transport modules
Date: Tue, 2 Nov 2021 19:51:30 +0900 [thread overview]
Message-ID: <YYEYMt543Hg+Hxzy@codewreck.org> (raw)
In-Reply-To: <20211017134611.4330-1-linux@weissschuh.net>
Hi,
Sorry for the late reply
Thomas Weißschuh wrote on Sun, Oct 17, 2021 at 03:46:11PM +0200:
> Automatically load transport modules based on the trans= parameter
> passed to mount.
> The removes the requirement for the user to know which module to use.
This looks good to me, I'll test this briefly on differnet config (=y,
=m) and submit to Linus this week for the next cycle.
Makes me wonder why trans_fd is included in 9pnet and not in a 9pnet-fd
or 9pnet-tcp module but that'll be for another time...
--
Dominique
next prev parent reply other threads:[~2021-11-02 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 13:46 [PATCH] net/9p: autoload transport modules Thomas Weißschuh
2021-11-02 10:51 ` Dominique Martinet [this message]
2021-11-02 10:59 ` Thomas Weißschuh
2021-11-02 11:51 ` Dominique Martinet
2021-11-02 14:49 ` Thomas Weißschuh
2021-11-02 14:58 ` Dominique Martinet
2021-11-02 15:32 ` Thomas Weißschuh
2021-11-02 23:17 ` Dominique Martinet
2021-11-02 23:33 ` Thomas Weißschuh
2021-11-03 0:26 ` Dominique Martinet
2021-11-03 1:00 ` 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=YYEYMt543Hg+Hxzy@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.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 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).