From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: bfields@fieldses.org, Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@openvz.org
Subject: [PATCH 0/6] Lockd: service start cleanup patch set
Date: Wed, 25 Apr 2012 18:22:32 +0400 [thread overview]
Message-ID: <20120425141934.22909.53047.stgit@localhost6.localdomain6> (raw)
This patch set simplifies LockD start logic, makes code looks straight-forward
and clear.
The following series consists of:
---
Stanislav Kinsbursky (6):
LockD: pass service to per-net up and down functions
LockD: use existent per-net data function on service creation
LockD: service creation function introduced
LockD: move global usage counter manipulation from error path
LockD: service start function introduced
LockD: add debug message to start and stop functions
fs/lockd/svc.c | 140 +++++++++++++++++++++++++++++++++-----------------------
1 files changed, 83 insertions(+), 57 deletions(-)
next reply other threads:[~2012-04-25 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 14:22 Stanislav Kinsbursky [this message]
2012-04-25 14:22 ` [PATCH 1/6] LockD: pass service to per-net up and down functions Stanislav Kinsbursky
2012-04-25 14:22 ` [PATCH 2/6] LockD: use existent per-net data function on service creation Stanislav Kinsbursky
2012-04-25 14:22 ` [PATCH 3/6] LockD: service creation function introduced Stanislav Kinsbursky
2012-04-25 14:23 ` [PATCH 4/6] LockD: move global usage counter manipulation from error path Stanislav Kinsbursky
2012-04-25 14:23 ` [PATCH 5/6] LockD: service start function introduced Stanislav Kinsbursky
2012-04-25 14:23 ` [PATCH 6/6] LockD: add debug message to start and stop functions Stanislav Kinsbursky
2012-05-09 19:08 ` [PATCH 0/6] Lockd: service start cleanup patch set J. Bruce Fields
2012-05-09 21:04 ` Stanislav Kinsbursky
2012-05-11 11:04 ` Stanislav Kinsbursky
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=20120425141934.22909.53047.stgit@localhost6.localdomain6 \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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).