From: Benny Halevy <bhalevy@tonian.com>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/10] pnfs-block ctl
Date: Mon, 05 Dec 2011 10:09:50 +0200 [thread overview]
Message-ID: <4EDC7C4E.1040901@tonian.com> (raw)
Folks,
The following are fixes to Rick McNeal's user-space ctl daemon
for the pnfs block server.
They are available on:
git://linux-nfs.org/~bhalevy/pnfsd-block-ctl.git
The daemon is required on the server side to get the pnfs
block device EFI signature and volume signature.
[PATCH 01/10] use gcc
[PATCH 02/10] efi: fix user-land debug printouts
[PATCH 03/10] ctl: improve debug printouts
[PATCH 04/10] increase compiler warning level
[PATCH 05/10] ctl: always return a value from find_dm_name
[PATCH 06/10] add missing includes
[PATCH 07/10] ctl: fix compiler warnings
[PATCH 08/10] fix compiler warnings around get_output use of argv
[PATCH 09/10] ctl: main should return 0 on success
[PATCH 10/10] efi: fix compiler warnings
next reply other threads:[~2011-12-05 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 8:09 Benny Halevy [this message]
2011-12-05 8:12 ` [PATCH 01/10] use gcc Benny Halevy
2011-12-05 8:13 ` [PATCH 02/10] efi: fix user-land debug printouts Benny Halevy
2011-12-05 8:13 ` [PATCH 03/10] ctl: improve " Benny Halevy
2011-12-05 8:13 ` [PATCH 04/10] increase compiler warning level Benny Halevy
2011-12-05 8:13 ` [PATCH 05/10] ctl: always return a value from find_dm_name Benny Halevy
2011-12-05 8:13 ` [PATCH 06/10] add missing includes Benny Halevy
2011-12-05 8:14 ` [PATCH 07/10] ctl: fix compiler warnings Benny Halevy
2011-12-05 8:14 ` [PATCH 08/10] fix compiler warnings around get_output use of argv Benny Halevy
2011-12-05 8:14 ` [PATCH 09/10] ctl: main should return 0 on success Benny Halevy
2011-12-05 8:14 ` [PATCH 10/10] efi: fix compiler warnings Benny Halevy
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=4EDC7C4E.1040901@tonian.com \
--to=bhalevy@tonian.com \
--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 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.