From: Dominique Martinet <asmadeus@codewreck.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Eric Sandeen <sandeen@sandeen.net>,
Eric Sandeen <sandeen@redhat.com>,
v9fs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, ericvh@kernel.org,
lucho@ionkov.net, linux_oss@crudebyte.com, dhowells@redhat.com
Subject: Re: [PATCH V2 0/4] 9p: convert to the new mount API
Date: Sat, 16 Aug 2025 05:53:08 +0900 [thread overview]
Message-ID: <aJ-eNBtjEuYidHiu@codewreck.org> (raw)
In-Reply-To: <20250815-gebohrt-stollen-b1747c01ce40@brauner>
Christian Brauner wrote on Fri, Aug 15, 2025 at 03:55:13PM +0200:
> Fyi, Eric (Sandeen) is talking about me, Christian Brauner, whereas you
> seem to be thinking of Christian Schoenebeck...
Ah, yes.. (He's also in cc, although is name doesn't show up in his
linux_oss@crudebyte mail)
Well, that makes more sense; I've picked up the patches now so I think
it's fine as it is but happy to drop the set if you have any reason to
want them, just let me know.
--
Dominique
next prev parent reply other threads:[~2025-08-15 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 19:18 Eric Sandeen
2025-07-30 19:18 ` [PATCH V2 1/4] fs/fs_parse: add back fsparam_u32hex Eric Sandeen
2025-07-30 19:18 ` [PATCH V2 2/4] net/9p: move structures and macros to header files Eric Sandeen
2025-07-30 19:18 ` [PATCH V2 3/4] 9p: create a v9fs_context structure to hold parsed options Eric Sandeen
2025-07-30 19:18 ` [PATCH V2 4/4] 9p: convert to the new mount API Eric Sandeen
2025-07-30 22:21 ` [PATCH V2 0/4] " asmadeus
2025-07-31 1:38 ` Eric Sandeen
2025-07-31 12:24 ` asmadeus
2025-08-14 16:55 ` Eric Sandeen
2025-08-15 1:49 ` Dominique Martinet
2025-08-15 2:45 ` Eric Sandeen
2025-08-15 13:55 ` Christian Brauner
2025-08-15 20:53 ` Dominique Martinet [this message]
2025-09-23 22:21 ` Eric Sandeen
2025-09-24 2:54 ` Dominique Martinet
2025-09-24 5:25 ` 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=aJ-eNBtjEuYidHiu@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®