From: Ian Kent <raven@themaw.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: autofs@vger.kernel.org
Subject: Re: [PATCH] fs: autofs: delete repeated words in comments
Date: Tue, 11 Aug 2020 16:36:17 +0800 [thread overview]
Message-ID: <75e04b06be0561c3cec936cd3bbc44fe82ca73f4.camel@themaw.net> (raw)
In-Reply-To: <20200811021817.24982-1-rdunlap@infradead.org>
On Mon, 2020-08-10 at 19:18 -0700, Randy Dunlap wrote:
> Drop duplicated words {the, at} in comments.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Ian Kent <raven@themaw.net>
> Cc: autofs@vger.kernel.org
Acked-by: Ian Kent <raven@themaw.net>
> ---
> fs/autofs/dev-ioctl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-next-20200807.orig/fs/autofs/dev-ioctl.c
> +++ linux-next-20200807/fs/autofs/dev-ioctl.c
> @@ -20,7 +20,7 @@
> * another mount. This situation arises when starting automount(8)
> * or other user space daemon which uses direct mounts or offset
> * mounts (used for autofs lazy mount/umount of nested mount trees),
> - * which have been left busy at at service shutdown.
> + * which have been left busy at service shutdown.
> */
>
> typedef int (*ioctl_fn)(struct file *, struct autofs_sb_info *,
> @@ -496,7 +496,7 @@ static int autofs_dev_ioctl_askumount(st
> * located path is the root of a mount we return 1 along with
> * the super magic of the mount or 0 otherwise.
> *
> - * In both cases the the device number (as returned by
> + * In both cases the device number (as returned by
> * new_encode_dev()) is also returned.
> */
> static int autofs_dev_ioctl_ismountpoint(struct file *fp,
next prev parent reply other threads:[~2020-08-11 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 2:18 Randy Dunlap
2020-08-11 8:36 ` Ian Kent [this message]
2020-08-11 14:42 ` Randy Dunlap
2020-08-12 0:03 ` Ian Kent
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=75e04b06be0561c3cec936cd3bbc44fe82ca73f4.camel@themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®