From: Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Dawei Li <set_pte_at@outlook.com>,
brauner@kernel.org, neilb@suse.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vfs: Make vfs_get_super() internal
Date: Mon, 31 Oct 2022 00:55:37 -0700 [thread overview]
Message-ID: <Y19/eSFnrSpnTHDf@infradead.org> (raw)
In-Reply-To: <Y17edxOrW81EBh1v@ZenIV>
On Sun, Oct 30, 2022 at 08:28:39PM +0000, Al Viro wrote:
> I would rather kill the "keying" thing completely.
And I replied with a patch doing just that to his v1. Guess it's time
to resend it formally.
prev parent reply other threads:[~2022-10-31 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 13:06 [PATCH v2] vfs: Make vfs_get_super() internal Dawei Li
2022-10-30 20:28 ` Al Viro
2022-10-31 7:55 ` Christoph Hellwig [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=Y19/eSFnrSpnTHDf@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=set_pte_at@outlook.com \
--cc=viro@zeniv.linux.org.uk \
/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).