[PATCH] dcache: fix typos in comments in dcache.h

[PATCH] dcache: fix typos in comments in dcache.h

[tahsina13]

---
 include/linux/dcache.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/linux/dcache.h b/include/linux/dcache.h
index c5bd5a74baba..72b57a15769c 100644
--- a/include/linux/dcache.h
+++ b/include/linux/dcache.h
@@ -172,7 +172,7 @@ struct dentry_operations {
  * Locking rules for dentry_operations callbacks are to be found in
  * Documentation/filesystems/locking.rst. Keep it updated!
  *
- * FUrther descriptions are found in Documentation/filesystems/vfs.rst.
+ * Further descriptions are found in Documentation/filesystems/vfs.rst.
  * Keep it updated too!
  */
 
@@ -233,7 +233,7 @@ enum dentry_flags {
 extern seqlock_t rename_lock;
 
 /*
- * These are the low-level FS interfaces to the dcache..
+ * These are the low-level FS interfaces to the dcache.
  */
 extern void d_instantiate(struct dentry *, struct inode *);
 extern void d_instantiate_new(struct dentry *, struct inode *);
-- 
2.43.0

Re: [PATCH] dcache: fix typos in comments in dcache.h

[Christian Brauner]

On Sat, 18 Apr 2026 14:47:04 -0400, tahsina13 wrote:
> 


Applied to the vfs-7.2.misc branch of the vfs/vfs.git tree.
Patches in the vfs-7.2.misc branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-7.2.misc

[1/1] dcache: fix typos in comments in dcache.h
      https://git.kernel.org/vfs/vfs/c/66814af18595

Re: [PATCH] dcache: fix typos in comments in dcache.h

[Christian Brauner]

On Sat, Apr 18, 2026 at 02:47:04PM -0400, tahsina13 wrote:


This is missing an SoB... So we can't take it.