From: Christoph Hellwig <hch@infradead.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Eugene Teo <eugene@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Bodo Eggert <7eggert@web.de>
Subject: Re: [PATCH v2] vfs: add NOFOLLOW flag to umount(2)
Date: Thu, 11 Feb 2010 12:21:00 -0500 [thread overview]
Message-ID: <20100211172100.GA28533@infradead.org> (raw)
In-Reply-To: <E1NfAXx-0000ln-59@pomaz-ex.szeredi.hu>
On Wed, Feb 10, 2010 at 12:15:53PM +0100, Miklos Szeredi wrote:
> - renamed flag to UMOUNT_NOFOLLOW
> - added UMOUNT_UNUSED for feature detection
Umm, why? MNT_ certainly isn't the best naming for unmount flags,
but switching convention after we had a few doesn't make any sense.
next prev parent reply other threads:[~2010-02-11 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 11:15 [PATCH v2] vfs: add NOFOLLOW flag to umount(2) Miklos Szeredi
2010-02-11 17:21 ` Christoph Hellwig [this message]
2010-02-11 18:06 ` Miklos Szeredi
2010-02-21 2:01 ` Al Viro
2010-02-22 20:29 ` Miklos Szeredi
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=20100211172100.GA28533@infradead.org \
--to=hch@infradead.org \
--cc=7eggert@web.de \
--cc=eugene@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mtk.manpages@gmail.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).