From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, autofs@linux.kernel.org
Subject: [PATCH 0/13] autofs4 - various cleanups, updates and bug fixes
Date: Wed, 18 Jan 2006 15:22:21 +0800 [thread overview]
Message-ID: <200601180722.k0I7MLTB006112@eagle.themaw.net> (raw)
Sincere appologies for the post without a Subject:
Here they are as they should be DOH!
This is the first set of patches for autofs in moving toward a
kernel <-> userspace communication protocol update.
The changes implemented in the patch set are:
1) lookup-cleanup - cleanup of whitespace and formating changes.
2) readdir-cleanup - changes readdir routines to use the cursor
based routines in libfs.c.
3) failed-lookup - fix stale dentrys stopping mounts.
4) expire-cleanup - change return values and names of two functions
to aid code readability.
5) expire-traversal-cleanup - simplify expire by adapting it to
use the "next_entry" function from namespace.c.
6) expire-tree-false-negative - fix an expire case which returns
busy on tree mounts when they are not.
7) expire-not-busy-only - alter expire semantics to match that
needed for a rework of autofs direct mounts.
8) remove-update_atime - remove update of atime in favour of
letting the VFS update it.
9) add-show_options - add show_options method to display autofs4
mount options in the proc filesystem.
10) waitq-cleanup - whitespace cleanup of waitq.c
11) rename-simple_empty_nolock - rename function according to
kernel conventions.
12) may_umount-to-boolean - change may_umount* functions to
boolean to aid code readability.
reply other threads:[~2006-01-18 7:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200601180722.k0I7MLTB006112@eagle.themaw.net \
--to=raven@themaw.net \
--cc=akpm@osdl.org \
--cc=autofs@linux.kernel.org \
--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).