From: Eric Sandeen <sandeen@redhat.com>
To: v9fs@lists.linux.dev
Cc: ericvh@kernel.org, lucho@ionkov.net, asmadeus@codewreck.org,
linux_oss@crudebyte.com, David Howells <dhowells@redhat.com>
Subject: Re: [RFC PATCH 3/4] 9p: create a v9fs_context structure to hold parsed options
Date: Sat, 26 Jul 2025 10:17:41 -0700 [thread overview]
Message-ID: <c19be9ba-d164-4d43-bc03-c467584df3c4@redhat.com> (raw)
In-Reply-To: <20250724023325.16178-4-sandeen@redhat.com>
On 7/23/25 9:23 PM, Eric Sandeen wrote:
> This patch creates a new v9fs_context structure which includes
> v9fs_session_info as well as p9_client, p9_fd_opts, and p9_rdma_opts
> to hold all parsed options. The new structure will be used in the next
> commit to pass all parsed options to the appropriate transports.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
> fs/9p/v9fs.h | 49 ---------------------
> include/net/9p/client.h | 88 ++++++++++++++++++++++++++++++++++++++
> include/net/9p/transport.h | 32 --------------
> 3 files changed, 88 insertions(+), 81 deletions(-)
This was a last-minute refactoring that I did not properly build-test,
it seems, I'll get it fixed up in the next version. Sorry about that.
-Eric
next prev parent reply other threads:[~2025-07-26 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 2:23 [RFC PATCH 0/4] 9p: convert to the new mount API Eric Sandeen
2025-07-24 2:23 ` [RFC PATCH 1/4] fs/fs_parse: add back fsparam_u32hex Eric Sandeen
2025-07-24 2:23 ` [RFC PATCH 2/4] net/9p: move structures and macros to header files Eric Sandeen
2025-07-24 2:23 ` [RFC PATCH 3/4] 9p: create a v9fs_context structure to hold parsed options Eric Sandeen
2025-07-26 17:17 ` Eric Sandeen [this message]
2025-07-26 18:32 ` Eric Sandeen
2025-07-24 2:23 ` [RFC PATCH 4/4] 9p: convert to the new mount API Eric Sandeen
2025-07-26 14:09 ` David Howells
2025-07-26 17:29 ` Eric Sandeen
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=c19be9ba-d164-4d43-bc03-c467584df3c4@redhat.com \
--to=sandeen@redhat.com \
--cc=asmadeus@codewreck.org \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--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.