Drop words accidentally written twice, reported by checkpatch.pl as a
possible repeated word.  Only touches comments, no code changes.

Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
 fs/netfs/direct_write.c | 2 +-
 include/linux/netfs.h   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/netfs/direct_write.c b/fs/netfs/direct_write.c
index c16fbad286a1..634a860f3ebb 100644
--- a/fs/netfs/direct_write.c
+++ b/fs/netfs/direct_write.c
@@ -247,7 +247,7 @@ ssize_t netfs_unbuffered_write_iter_locked(struct kiocb *iocb, struct iov_iter *
 		/* If this is an async op and we're not using a bounce buffer,
 		 * we have to save the source buffer as the iterator is only
 		 * good until we return.  In such a case, extract an iterator
-		 * to represent as much of the the output buffer as we can
+		 * to represent as much of the output buffer as we can
 		 * manage.  Note that the extraction might not be able to
 		 * allocate a sufficiently large bvec array and may shorten the
 		 * request.
diff --git a/include/linux/netfs.h b/include/linux/netfs.h
index f837a501008c..fc6e76102642 100644
--- a/include/linux/netfs.h
+++ b/include/linux/netfs.h
@@ -627,7 +627,7 @@ static inline void netfs_write_zero_point(struct inode *inode,
  * @inode: The inode to access
  * @i_size: Where to return the local file size.
  * @remote_i_size: Where to return the size of the file on the server
- * @zero_point: Where to return the the point beyond which the server has no data
+ * @zero_point: Where to return the point beyond which the server has no data
  *
  * Read remote_i_size and zero_point safely without the potential for tearing
  * on 32-bit arches.
-- 
2.48.1