From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: autofs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] clean-up patch for autofs4
Date: Fri, 18 Jul 2014 10:48:28 +1000 [thread overview]
Message-ID: <20140718004353.19389.48104.stgit@notabene.brown> (raw)
Hi Andrew,
I believe you shepherd autofs4 patches at present.
The following 5 patches are some simple cleanups.
4 are trivial. One (the third) is a very simple optimization
which will be more important after the next patch set, but
is simple enough to be included now.
The next patch set will make autofs4 RCU-walk friendly so that in the
common case a filename lookup can walk across an autofs4 filesystem
without taking spinlocks or refcounts. I'll submit that once more
testing and review have convinced Ian and myself that it is ready.
Thanks,
NeilBrown
---
NeilBrown (5):
autofs4: remove unused autofs4_ispending()
autofs4: remove a redundant assignment
autofs4: don't take spinlock when not needed in autofs4_lookup_expiring
autofs4: remove some unused inline functions.
autofs4: comment typo: remove a a doubled word.
fs/autofs4/autofs_i.h | 63 -------------------------------------------------
fs/autofs4/expire.c | 1 -
fs/autofs4/root.c | 10 +++++---
3 files changed, 7 insertions(+), 67 deletions(-)
--
Signature
next reply other threads:[~2014-07-18 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 0:48 NeilBrown [this message]
2014-07-18 0:48 ` [PATCH 3/5] autofs4: don't take spinlock when not needed in autofs4_lookup_expiring NeilBrown
2014-07-18 0:48 ` [PATCH 2/5] autofs4: remove a redundant assignment NeilBrown
2014-07-18 0:48 ` [PATCH 1/5] autofs4: remove unused autofs4_ispending() NeilBrown
2014-07-18 0:48 ` [PATCH 4/5] autofs4: remove some unused inline functions NeilBrown
2014-07-18 0:48 ` [PATCH 5/5] autofs4: comment typo: remove a a doubled word NeilBrown
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=20140718004353.19389.48104.stgit@notabene.brown \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=autofs@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
all inboxes | Powered by JetHome®