autofs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Tomohiro Kusumi <kusumi.tomohiro@gmail.com>
Cc: autofs@vger.kernel.org
Subject: Re: [PATCH] autofs: Fix typos in Documentation/filesystems/autofs4.txt
Date: Thu, 07 Jul 2016 12:26:25 +0800	[thread overview]
Message-ID: <1467865585.3206.14.camel@themaw.net> (raw)
In-Reply-To: <1467484618-1908-1-git-send-email-kusumi.tomohiro@gmail.com>

On Sun, 2016-07-03 at 03:36 +0900, Tomohiro Kusumi wrote:
> plus minor whitespace fixes.

Also added to my patch queue.

It's great you are looking around in here.

I had completely forgotten about the interface documentation and this file needs
to be renamed as well for my autofs4 -> autofs rename series.

> 
> Signed-off-by: Tomohiro Kusumi <kusumi.tomohiro@gmail.com>
> ---
>  Documentation/filesystems/autofs4.txt | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/filesystems/autofs4.txt
> b/Documentation/filesystems/autofs4.txt
> index 39d02e1..8fac3fe 100644
> --- a/Documentation/filesystems/autofs4.txt
> +++ b/Documentation/filesystems/autofs4.txt
> @@ -203,9 +203,9 @@ initiated or is being considered, otherwise it returns 0.
>  Mountpoint expiry
>  -----------------
>  
> -The VFS has a mechansim for automatically expiring unused mounts,
> +The VFS has a mechanism for automatically expiring unused mounts,
>  much as it can expire any unused dentry information from the dcache.
> -This is guided by the MNT_SHRINKABLE flag.  This  only applies to
> +This is guided by the MNT_SHRINKABLE flag.  This only applies to
>  mounts that were created by `d_automount()` returning a filesystem to be
>  mounted.  As autofs doesn't return such a filesystem but leaves the
>  mounting to the automount daemon, it must involve the automount daemon
> @@ -298,7 +298,7 @@ remove directories and symlinks using normal filesystem
> operations.
>  autofs knows whether a process requesting some operation is the daemon
>  or not based on its process-group id number (see getpgid(1)).
>  
> -When an autofs filesystem it mounted the pgid of the mounting
> +When an autofs filesystem is mounted the pgid of the mounting
>  processes is recorded unless the "pgrp=" option is given, in which
>  case that number is recorded instead.  Any request arriving from a
>  process in that process group is considered to come from the daemon.
> @@ -450,7 +450,7 @@ Commands are:
>      numbers for existing filesystems can be found in
>      `/proc/self/mountinfo`.
>  - **AUTOFS_DEV_IOCTL_CLOSEMOUNT_CMD**: same as `close(ioctlfd)`.
> -- **AUTOFS_DEV_IOCTL_SETPIPEFD_CMD**: if the  filesystem is in
> +- **AUTOFS_DEV_IOCTL_SETPIPEFD_CMD**: if the filesystem is in
>      catatonic mode, this can provide the write end of a new pipe
>      in `arg1` to re-establish communication with a daemon.  The
>      process group of the calling process is used to identify the
--
To unsubscribe from this list: send the line "unsubscribe autofs" in

      reply	other threads:[~2016-07-07  4:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02 18:36 [PATCH] autofs: Fix typos in Documentation/filesystems/autofs4.txt Tomohiro Kusumi
2016-07-07  4:26 ` Ian Kent [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=1467865585.3206.14.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=kusumi.tomohiro@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).