From: Jeff Mahoney <jeffm@suse.com>
To: Al Viro <viro@ZenIV.linux.org.uk>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>
Subject: [PATCH] Documentation: Fix bad merge with tmpfile documentation
Date: Tue, 16 Jul 2013 10:19:26 -0400 [thread overview]
Message-ID: <51E5566E.7030607@suse.com> (raw)
Commit 48bde8d3 (Document ->tmpfile()) had a bad merge in vfs.txt,
where it put the new tmpfile prototype in the middle of the atomic_open
prototype.
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
---
Documentation/filesystems/vfs.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--- a/Documentation/filesystems/vfs.txt 2013-07-16 00:53:43.791018403 -0400
+++ b/Documentation/filesystems/vfs.txt 2013-07-16 00:59:16.008721223 -0400
@@ -360,11 +360,10 @@ struct inode_operations {
int (*removexattr) (struct dentry *, const char *);
void (*update_time)(struct inode *, struct timespec *, int);
int (*atomic_open)(struct inode *, struct dentry *,
- int (*tmpfile) (struct inode *, struct dentry *, umode_t);
-} ____cacheline_aligned;
struct file *, unsigned open_flag,
umode_t create_mode, int *opened);
-};
+ int (*tmpfile) (struct inode *, struct dentry *, umode_t);
+} ____cacheline_aligned;
Again, all methods are called without any locks being held, unless
otherwise noted.
--
Jeff Mahoney
SUSE Labs
reply other threads:[~2013-07-16 14:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51E5566E.7030607@suse.com \
--to=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.