From: Al Viro <viro@ZenIV.linux.org.uk>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH] bfs_lookup(): use d_splice_alias()
Date: Sun, 13 May 2018 22:13:43 +0100 [thread overview]
Message-ID: <20180513211343.GU30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <E1fHyHC-0007X1-RM@ZenIV.linux.org.uk>
Arrrrghh... Buggered script, sorry for bogus Cc lists...
prev parent reply other threads:[~2018-05-13 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 21:11 [RFC][PATCH] bfs_lookup(): use d_splice_alias() Al Viro
2018-05-13 21:13 ` Al Viro [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=20180513211343.GU30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ftp.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).