From: Dominique Martinet <asmadeus@codewreck.org>
To: "Matúš Škvarla" <skvarlamatus@gmail.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
ericvh@kernel.org, lucho@ionkov.net, linux_oss@crudebyte.com,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
sgarzare@redhat.com
Subject: Re: [PATCH v2] net/9p: add vsock transport
Date: Fri, 3 Jul 2026 23:16:04 +0900 [thread overview]
Message-ID: <akfEJIwxoVx1hKXd@codewreck.org> (raw)
In-Reply-To: <CANG_AsJtiN+31UCEZDSRX5ckq10vW-Qw7gjcBcB+feDZA7rgww@mail.gmail.com>
Matúš Škvarla wrote on Fri, Jul 03, 2026 at 02:31:41PM +0200:
> pi 3. 7. 2026 o 7:41 Stefan Hajnoczi <stefanha@redhat.com> napísal(a):
>
> > If you respin this patch, please add the port= option because it is
> > absent from this example and it could be missed if one doesn't read the
> > paragraph below carefully:
> >
> > mount -t 9p -o trans=vsock[,port=<port>] <CID> /mnt/9
> >
>
> My first idea was to have it there, but I removed it before submitting
> as I thought it would be redundant. No problem with having the port
> option specified in the example. I'll submit a v3 with this change.
If that's the only change required I can do it when applying, don't
bother with a v3 just yet
(didn't check the patch itself yet, will probably take a couple of
weeks...)
--
Dominique Martinet | Asmadeus
next prev parent reply other threads:[~2026-07-03 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 15:59 [PATCH v2] net/9p: add vsock transport skvarlamatus
2026-07-03 5:41 ` Stefan Hajnoczi
[not found] ` <CANG_AsJtiN+31UCEZDSRX5ckq10vW-Qw7gjcBcB+feDZA7rgww@mail.gmail.com>
2026-07-03 14:16 ` Dominique Martinet [this message]
2026-07-03 14:58 ` skvarlamatus
2026-07-03 14:16 ` Matus Skvarla
2026-07-03 14:39 ` Matus Skvarla
2026-07-03 9:12 ` Stefano Garzarella
2026-07-03 14:31 ` skvarlamatus
2026-07-03 14:39 ` Stefano Garzarella
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=akfEJIwxoVx1hKXd@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=sgarzare@redhat.com \
--cc=skvarlamatus@gmail.com \
--cc=stefanha@redhat.com \
--cc=v9fs@lists.linux.dev \
/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.