From: Scott Mayhew <smayhew@redhat.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [nfs-utils PATCH 0/3] A few small nfsdcld fixes
Date: Tue, 26 Nov 2019 10:47:15 -0500 [thread overview]
Message-ID: <20191126154718.22645-1-smayhew@redhat.com> (raw)
The first two patches fix problems I noticed when trying to build an rpm
package w/ nfsdcld enabled. The third patch fixes an issue I found
trying to use nfsdcld on a ppc64le system.
Scott Mayhew (3):
nfsdcld: don't override sbindir
systemd: install nfsdcld.service when nfsdcld is enabled
nfsdcld: getopt_long() returns an int, not a char
systemd/Makefile.am | 5 +++++
utils/nfsdcld/Makefile.am | 4 ----
utils/nfsdcld/nfsdcld.c | 2 +-
3 files changed, 6 insertions(+), 5 deletions(-)
--
2.17.2
next reply other threads:[~2019-11-26 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 15:47 Scott Mayhew [this message]
2019-11-26 15:47 ` [nfs-utils PATCH 1/3] nfsdcld: don't override sbindir Scott Mayhew
2019-11-26 15:47 ` [nfs-utils PATCH 2/3] systemd: install nfsdcld.service when nfsdcld is enabled Scott Mayhew
2019-11-26 15:47 ` [nfs-utils PATCH 3/3] nfsdcld: getopt_long() returns an int, not a char Scott Mayhew
2019-12-09 15:57 ` [nfs-utils PATCH 0/3] A few small nfsdcld fixes 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=20191126154718.22645-1-smayhew@redhat.com \
--to=smayhew@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox