From: Al Viro <viro@zeniv.linux.org.uk>
To: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: brauner@kernel.org, linux-fsdevel@vger.kernel.org,
Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: fix doc comment typo fs tree wide
Date: Mon, 18 Dec 2023 23:18:59 +0000 [thread overview]
Message-ID: <20231218231859.GV1674809@ZenIV> (raw)
In-Reply-To: <20231215130927.136917-1-aleksandr.mikhalitsyn@canonical.com>
On Fri, Dec 15, 2023 at 02:09:27PM +0100, Alexander Mikhalitsyn wrote:
> Do the replacement:
> s/simply passs @nop_mnt_idmap/simply passs @nop_mnt_idmap/
^^^ ^^^
> in the fs/ tree.
You might want to spell it correctly in the replacement string ;-)
next prev parent reply other threads:[~2023-12-18 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 13:09 [PATCH] fs: fix doc comment typo fs tree wide Alexander Mikhalitsyn
2023-12-15 13:44 ` Jan Kara
2023-12-15 14:03 ` Christian Brauner
2023-12-18 23:18 ` Al Viro [this message]
2023-12-19 9:32 ` Christian Brauner
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=20231218231859.GV1674809@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--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 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).