From: NeilBrown <neilb@suse.de>
To: Ian Kent <raven@themaw.net>
Cc: autofs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] autofs: the documentation I wanted to read
Date: Tue, 19 Aug 2014 17:00:26 +1000 [thread overview]
Message-ID: <20140819170026.5a8600a5@notabene.brown> (raw)
In-Reply-To: <1408356832.2533.5.camel@perseus.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]
On Mon, 18 Aug 2014 18:13:52 +0800 Ian Kent <raven@themaw.net> wrote:
> > +The available ioctl commands are:
> > +
> > +- **AUTOFS_IOC_READY**: a notification has been handled. The argument
> > + to the ioctl command is the "wait_queue_token" number
> > + corresponding to the notification being acknowledged.
> > +- **AUTOFS_IOC_FAIL**: similar to above, but indicates failure with
> > + the error code `ENOENT`.
> > +- **AUTOFS_IOC_CATATONIC**: Causes the autofs to enter "catatonic"
> > + mode meaning that it stops sending notifications to the daemon.
> > + This mode is also entered if a write to the pipe fails.
> > +- **AUTOFS_IOC_PROTOVER**: This returns the protocol version in use.
> > +- **AUTOFS_IOC_PROTOSUBVER**: Returns the protocol sub-version which
> > + is really a version number for the implementation. It is
> > + currently 2.
> > +- **AUTOFS_IOC_SETTIMEOUT**: This passes a pointer to an unsigned
> > + long. The value is used to set the timeout for expiry, and
> > + the current timeout value is stored back through the pointer.
> > +- **AUTOFS_IOC_ASKUMOUNT**: Returns, in the pointed-to `int`, 1 if
> > + the filesystem could be unmounted. This is only a hint as
> > + the situation could change at any instant. This call can be
> > + use to avoid a more expensive full unmount attempt.
> > +- **AUTOFS_IOC_EXPIRE**: as described above, this asks if there is
> > + anything suitable to expire. A pointer to a packet:
> > +
> > + struct autofs_packet_expire_multi {
> > + int proto_version; /* Protocol version */
> > + int type; /* Type of packet */
> > + autofs_wqt_t wait_queue_token;
> > + int len;
> > + char name[NAME_MAX+1];
>
> These fields have leading <spaces><tab> StGit complains about on import.
> Think it should be <tab><tab>.
>
I think I did that because I thought it would work better for markdown
processors (e.g. markdown_py).
However I just tested, and it works best if I turn all the tabs to spaces.
So that is what I have done.
And no rush with testing etc - I just wanted to make sure you had current
code now that -rc1 was out.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-08-19 7:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 6:33 [PATCH 0/5] RCU-walk support for autofs NeilBrown
2014-08-18 6:33 ` [PATCH 1/5] autofs4: allow RCU-walk to walk through autofs4 NeilBrown
2014-08-18 6:33 ` [PATCH 5/5] autofs: the documentation I wanted to read NeilBrown
2014-08-18 10:13 ` Ian Kent
2014-08-19 7:00 ` NeilBrown [this message]
2014-08-18 6:33 ` [PATCH 3/5] autofs4: avoid taking fs_lock during rcu-walk NeilBrown
2014-08-18 6:33 ` [PATCH 4/5] autofs4: d_manage() should return -EISDIR when appropriate in rcu-walk mode NeilBrown
2014-08-18 6:33 ` [PATCH 2/5] autofs4: factor should_expire() out of autofs4_expire_indirect NeilBrown
2014-08-18 8:25 ` [PATCH 0/5] RCU-walk support for autofs Ian Kent
2014-08-19 10:02 ` Ian Kent
2014-08-19 11:16 ` NeilBrown
2014-08-19 12:30 ` Ian Kent
2014-08-19 12:36 ` Ian Kent
2014-08-20 3:13 ` NeilBrown
2014-08-20 3:42 ` Ian Kent
2014-08-20 3:50 ` Ian Kent
2014-08-20 9:52 ` 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=20140819170026.5a8600a5@notabene.brown \
--to=neilb@suse.de \
--cc=autofs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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.