linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] ntfs3: Rename NTFS_FLAGS_LOG_REPLAING to NTFS_FLAGS_LOG_REPLAYING
Date: Fri, 28 Aug 2020 09:39:05 -0700	[thread overview]
Message-ID: <4434fdd9d747a0c911d8c0d45eb12e26c16ab7d6.1598632661.git.joe@perches.com> (raw)
In-Reply-To: <cover.1598632661.git.joe@perches.com>

Use the correct spelling of REPLAY

Signed-off-by: Joe Perches <joe@perches.com>
---
 fs/ntfs3/frecord.c | 2 +-
 fs/ntfs3/fsntfs.c  | 4 ++--
 fs/ntfs3/inode.c   | 2 +-
 fs/ntfs3/ntfs_fs.h | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/fs/ntfs3/frecord.c b/fs/ntfs3/frecord.c
index 77a9a46d1510..13454de34c21 100644
--- a/fs/ntfs3/frecord.c
+++ b/fs/ntfs3/frecord.c
@@ -2177,7 +2177,7 @@ int ni_write_inode(struct inode *inode, int sync, const char *hint)
 	upd_parent = ni->ni_flags & NI_FLAG_UPDATE_PARENT;
 	rec = ni->mi.mrec;
 
-	if (!is_rec_inuse(rec) || (sbi->flags & NTFS_FLAGS_LOG_REPLAING))
+	if (!is_rec_inuse(rec) || (sbi->flags & NTFS_FLAGS_LOG_REPLAYING))
 		goto write_subrecords;
 
 	if (!inode->i_nlink)
diff --git a/fs/ntfs3/fsntfs.c b/fs/ntfs3/fsntfs.c
index 9c489e8be91a..10cc86ee85b8 100644
--- a/fs/ntfs3/fsntfs.c
+++ b/fs/ntfs3/fsntfs.c
@@ -249,7 +249,7 @@ int ntfs_loadlog_and_replay(struct ntfs_inode *ni, struct ntfs_sb_info *sbi)
 		goto out;
 	}
 
-	sbi->flags |= NTFS_FLAGS_LOG_REPLAING;
+	sbi->flags |= NTFS_FLAGS_LOG_REPLAYING;
 
 	ref.low = cpu_to_le32(MFT_REC_MFT);
 	ref.high = 0;
@@ -309,7 +309,7 @@ int ntfs_loadlog_and_replay(struct ntfs_inode *ni, struct ntfs_sb_info *sbi)
 	}
 
 out:
-	sbi->flags &= ~NTFS_FLAGS_LOG_REPLAING;
+	sbi->flags &= ~NTFS_FLAGS_LOG_REPLAYING;
 
 	return err;
 }
diff --git a/fs/ntfs3/inode.c b/fs/ntfs3/inode.c
index 3e66ad89d2fd..2f443bd151b0 100644
--- a/fs/ntfs3/inode.c
+++ b/fs/ntfs3/inode.c
@@ -75,7 +75,7 @@ static struct inode *ntfs_read_mft(struct inode *inode,
 
 	rec = ni->mi.mrec;
 
-	if (sbi->flags & NTFS_FLAGS_LOG_REPLAING) {
+	if (sbi->flags & NTFS_FLAGS_LOG_REPLAYING) {
 		;
 	} else if (ref->seq != rec->seq) {
 		err = -EINVAL;
diff --git a/fs/ntfs3/ntfs_fs.h b/fs/ntfs3/ntfs_fs.h
index 066c5d0549b1..0239fe7c6527 100644
--- a/fs/ntfs3/ntfs_fs.h
+++ b/fs/ntfs3/ntfs_fs.h
@@ -143,7 +143,7 @@ struct ntfs_index {
 };
 
 /* Set when $LogFile is replaying */
-#define NTFS_FLAGS_LOG_REPLAING 0x00000008
+#define NTFS_FLAGS_LOG_REPLAYING 0x00000008
 
 /* Set when we changed first MFT's which copy must be updated in $MftMirr */
 #define NTFS_FLAGS_MFTMIRR 0x00001000
-- 
2.26.0


      parent reply	other threads:[~2020-08-28 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 16:39 [PATCH 0/3] ntfs3: trivial style cleanups Joe Perches
2020-08-28 16:39 ` [PATCH 1/3] ntfs3: Add and use logging macros Joe Perches
2020-08-28 16:39 ` [PATCH 2/3] ntfs3: Use more common brace style Joe Perches
2020-08-28 16:39 ` Joe Perches [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=4434fdd9d747a0c911d8c0d45eb12e26c16ab7d6.1598632661.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).