From: asomers@FreeBSD.org
To: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, Nikolaus@rath.org
Cc: Alan Somers <asomers@FreeBSD.org>
Subject: [PATCH 2/3] fuse: fix changelog entry for protocol 7.12
Date: Fri, 19 Apr 2019 15:42:45 -0600 [thread overview]
Message-ID: <20190419214246.26290-2-asomers@FreeBSD.org> (raw)
In-Reply-To: <20190419214246.26290-1-asomers@FreeBSD.org>
From: Alan Somers <asomers@FreeBSD.org>
This was a mistake in the comment in commit e0a43ddcc08c.
Signed-off-by: Alan Somers <asomers@FreeBSD.org>
---
include/uapi/linux/fuse.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/uapi/linux/fuse.h b/include/uapi/linux/fuse.h
index e4ceeb406eb3..6457036a5960 100644
--- a/include/uapi/linux/fuse.h
+++ b/include/uapi/linux/fuse.h
@@ -54,7 +54,7 @@
* - add POLL message and NOTIFY_POLL notification
*
* 7.12
- * - add umask flag to input argument of open, mknod and mkdir
+ * - add umask flag to input argument of create, mknod and mkdir
* - add notification messages for invalidation of inodes and
* directory entries
*
--
2.21.0
next prev parent reply other threads:[~2019-04-19 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 21:42 [PATCH 1/3] fuse: document fuse_fsync_in.fsync_flags asomers
2019-04-19 21:42 ` asomers [this message]
2019-04-19 21:42 ` [PATCH 3/3] fuse: fix changelog entry for protocol 7.9 asomers
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=20190419214246.26290-2-asomers@FreeBSD.org \
--to=asomers@freebsd.org \
--cc=Nikolaus@rath.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).