From: Dominique Martinet <asmadeus@codewreck.org>
To: Changbin Du <changbin.du@gmail.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH v3 0/3] 9p: add support for root file systems
Date: Sun, 20 Jun 2021 13:16:00 +0900 [thread overview]
Message-ID: <YM7BAM5lK7NRVZ7n@codewreck.org> (raw)
In-Reply-To: <20210620033659.s7rohai7dzwpgjur@mail.google.com>
Changbin Du wrote on Sun, Jun 20, 2021 at 11:36:59AM +0800:
> The main problem is we lack a generic handing for non-block rootdev. I think
> maybe we can unify all of above.
We're already going in that direction, please have a look at the threads
on fsdevel:
(new patch by Christoph)
https://lore.kernel.org/linux-fsdevel/20210617153649.1886693-1-hch@lst.de/
(older threads I linked earlier)
https://lore.kernel.org/linux-fsdevel/20210608153524.GB504497@redhat.com/
I think it's getting there, Christoph should send a v2 addressing Vivek
remarks that will likely get picked up.
--
Dominique
prev parent reply other threads:[~2021-06-20 4:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 23:09 [PATCH v3 0/3] 9p: add support for root file systems Changbin Du
2021-06-06 23:09 ` [PATCH v3 1/3] " Changbin Du
2021-06-07 1:06 ` kernel test robot
2021-06-14 1:09 ` Changbin Du
2021-06-06 23:09 ` [PATCH v3 2/3] 9p: doc: move to a new dedicated folder Changbin Du
2021-06-06 23:09 ` [PATCH v3 3/3] 9p: doc: add v9fsroot description Changbin Du
2021-06-06 23:45 ` [PATCH v3 0/3] 9p: add support for root file systems Dominique Martinet
2021-06-14 8:57 ` Josh Triplett
2021-06-14 9:01 ` Dominique Martinet
2021-06-14 9:19 ` Josh Triplett
2021-06-20 3:36 ` Changbin Du
2021-06-20 4:16 ` Dominique Martinet [this message]
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=YM7BAM5lK7NRVZ7n@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=changbin.du@gmail.com \
--cc=ericvh@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--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