summaryrefslogtreecommitdiff
path: root/fs/aufs/i_op_ren.c
diff options
context:
space:
mode:
authorAndré Fabian Silva Delgado <emulatorman@parabola.nu>2015-10-27 13:37:40 -0300
committerAndré Fabian Silva Delgado <emulatorman@parabola.nu>2015-10-27 13:37:40 -0300
commitbadc0e42604c4465facd81d2323e98b3b1eb9188 (patch)
treee61811e7ddf70517f4b546d522ba3b630b38f50f /fs/aufs/i_op_ren.c
parentf19866e5cb04f8f007cb422132ea4611cdacc8e3 (diff)
Linux-libre 4.2.4-gnupck-4.2.4-gnu
Diffstat (limited to 'fs/aufs/i_op_ren.c')
-rw-r--r--fs/aufs/i_op_ren.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/aufs/i_op_ren.c b/fs/aufs/i_op_ren.c
index 132301251..652e973ce 100644
--- a/fs/aufs/i_op_ren.c
+++ b/fs/aufs/i_op_ren.c
@@ -77,7 +77,7 @@ struct au_ren_args {
/*
* functions for reverting.
* when an error happened in a single rename systemcall, we should revert
- * everything as if nothing happend.
+ * everything as if nothing happened.
* we don't need to revert the copied-up/down the parent dir since they are
* harmless.
*/
@@ -859,7 +859,7 @@ int aufs_rename(struct inode *_src_dir, struct dentry *_src_dentry,
/*
* is it possible?
- * yes, it happend (in linux-3.3-rcN) but I don't know why.
+ * yes, it happened (in linux-3.3-rcN) but I don't know why.
* there may exist a problem somewhere else.
*/
err = -EINVAL;