All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 5/5] d_path.c: typo fix...
Date: Thu, 18 Aug 2022 03:59:58 +0100	[thread overview]
Message-ID: <Yv2rLgc9NruwfwR6@ZenIV> (raw)
In-Reply-To: <Yv2qoNQg48rtymGE@ZenIV>

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
 fs/d_path.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/d_path.c b/fs/d_path.c
index ce8d9d49e1e7..56a6ee4c6331 100644
--- a/fs/d_path.c
+++ b/fs/d_path.c
@@ -34,7 +34,7 @@ static bool prepend_char(struct prepend_buffer *p, unsigned char c)
 }
 
 /*
- * The source of the prepend data can be an optimistoc load
+ * The source of the prepend data can be an optimistic load
  * of a dentry name and length. And because we don't hold any
  * locks, the length and the pointer to the name may not be
  * in sync if a concurrent rename happens, and the kernel
-- 
2.30.2


      parent reply	other threads:[~2022-08-18  3:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  2:57 [PATCH 1/5] dynamic_dname(): drop unused dentry argument Al Viro
2022-08-18  2:58 ` [PATCH 2/5] ksmbd: don't open-code file_path() Al Viro
2022-08-18  6:19   ` Namjae Jeon
2022-08-18  2:58 ` [PATCH 3/5] ->getprocattr(): attribute name is const char *, TYVM Al Viro
2022-08-18 18:34   ` Schaufler, Casey
2022-08-26  7:45   ` Christian Brauner
2022-08-18  2:59 ` [PATCH 4/5] ksmbd: don't open-code %pf Al Viro
2022-08-18  6:08   ` Namjae Jeon
2022-08-18 20:35     ` Al Viro
2022-08-18 23:26       ` Namjae Jeon
2022-08-20  3:47         ` Al Viro
2022-08-20  5:44           ` Namjae Jeon
2022-08-20 15:33             ` Al Viro
2022-08-21  2:06               ` Steve French
2022-08-18  2:59 ` Al Viro [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=Yv2rLgc9NruwfwR6@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.