summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2019-06-28 19:27:29 -0700
committerDarrick J. Wong <darrick.wong@oracle.com>2019-06-28 19:27:29 -0700
commit086252c34bc2c984e6be5f939efcc4c9616c22e1 (patch)
treeb9bab138ad53ecb7eabbc0db514c259f66aeee7d
parentdbd329f1e44ed48de8a1c19da5eb1218f5e1b4a5 (diff)
downloadtalos-op-linux-086252c34bc2c984e6be5f939efcc4c9616c22e1.tar.gz
talos-op-linux-086252c34bc2c984e6be5f939efcc4c9616c22e1.zip
xfs: fix a trivial comment typo in xfs_trans_committed_bulk
Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Brian Foster <bfoster@redhat.com> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
-rw-r--r--fs/xfs/xfs_trans.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/xfs/xfs_trans.c b/fs/xfs/xfs_trans.c
index 0746b329a937..91bb46c6cc2b 100644
--- a/fs/xfs/xfs_trans.c
+++ b/fs/xfs/xfs_trans.c
@@ -815,7 +815,7 @@ xfs_log_item_batch_insert(
*
* If we are called with the aborted flag set, it is because a log write during
* a CIL checkpoint commit has failed. In this case, all the items in the
- * checkpoint have already gone through iop_commited and iop_unlock, which
+ * checkpoint have already gone through iop_committed and iop_unlock, which
* means that checkpoint commit abort handling is treated exactly the same
* as an iclog write error even though we haven't started any IO yet. Hence in
* this case all we need to do is iop_committed processing, followed by an
OpenPOWER on IntegriCloud