From: Chuck Lever <chuck.lever@oracle.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] Two short fixes for sm-notify
Date: Mon, 15 Mar 2010 13:51:27 -0400 [thread overview]
Message-ID: <20100315174453.2586.40876.stgit@localhost.localdomain> (raw)
Hi Steve-
These address two minor shortcomings when sending SM_NOTIFY requests
during reboot recovery. Please consider these for the next nfs-utils
release.
---
Chuck Lever (2):
sm-notify: Send fully-qualified and unqualified mon_names
sm-notify: Use my_name when sending SM_NOTIFY requests
utils/statd/sm-notify.c | 62 ++++++++++++++++++++++++++++++++++++---------
utils/statd/sm-notify.man | 28 +++++++++-----------
utils/statd/statd.man | 14 +---------
3 files changed, 64 insertions(+), 40 deletions(-)
--
Chuck Lever
next reply other threads:[~2010-03-15 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 17:51 Chuck Lever [this message]
[not found] ` <20100315174453.2586.40876.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-03-15 17:51 ` [PATCH 1/2] sm-notify: Use my_name when sending SM_NOTIFY requests Chuck Lever
[not found] ` <20100315175137.2586.71894.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-03-15 22:25 ` Jeff Layton
[not found] ` <20100315182535.2aacdadb-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-03-16 4:12 ` Chuck Lever
2010-03-16 11:20 ` Jeff Layton
2010-03-15 17:51 ` [PATCH 2/2] sm-notify: Send fully-qualified and unqualified mon_names Chuck Lever
[not found] ` <20100315175145.2586.1215.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-03-15 22:30 ` Jeff Layton
2010-03-17 10:36 ` Steve Dickson
[not found] ` <4BA0B0A4.6020705-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-03-17 14:39 ` Chuck Lever
2010-03-19 20:03 ` Steve Dickson
2010-03-17 10:53 ` [PATCH 0/2] Two short fixes for sm-notify Steve Dickson
[not found] ` <4BA0B48E.8030504-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-03-17 14:29 ` Chuck Lever
2010-03-19 20:05 ` Steve Dickson
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=20100315174453.2586.40876.stgit@localhost.localdomain \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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 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.