From: Patrick Steinhardt <ps@pks.im>
To: linux-nfs@vger.kernel.org
Cc: Patrick Steinhardt <ps@pks.im>
Subject: [PATCH 5/6] nfsd_path: Include missing header for `struct stat`
Date: Wed, 28 Aug 2019 09:10:16 +0200 [thread overview]
Message-ID: <c4efa52412e2ff0e9079bf88ab94d8e366bf8f8f.1566976047.git.ps@pks.im> (raw)
In-Reply-To: <cover.1566976047.git.ps@pks.im>
The header "nfsd_path.h" uses `struct stat` in its function signatures,
but doesn't include the <sys/stat.h> header. This may cause compiler
warnings if a compilation unit includes "nfsd_path.h" while not
transitively including <sys/stat.h>.
Fix the potential warning by including <sys/stat.h> in the header.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
---
support/include/nfsd_path.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/support/include/nfsd_path.h b/support/include/nfsd_path.h
index ca2570a9..b42416bb 100644
--- a/support/include/nfsd_path.h
+++ b/support/include/nfsd_path.h
@@ -4,6 +4,8 @@
#ifndef NFSD_PATH_H
#define NFSD_PATH_H
+#include <sys/stat.h>
+
void nfsd_path_init(void);
const char * nfsd_path_nfsd_rootdir(void);
--
2.23.0
next prev parent reply other threads:[~2019-08-28 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:10 [PATCH 0/6] Fixes for various compiler warnings Patrick Steinhardt
2019-08-28 7:10 ` [PATCH 1/6] Annotate unused fields with UNUSED Patrick Steinhardt
2019-08-28 7:10 ` [PATCH 2/6] Use <fcntl.h> header instead of <sys/fcntl.h> Patrick Steinhardt
2019-08-28 7:10 ` [PATCH 3/6] Use <poll.h> header instead of <sys/poll.h> Patrick Steinhardt
2019-08-28 7:10 ` [PATCH 4/6] configure.ac: Add <sys/socket.h> header when checking sizeof(socklen_t) Patrick Steinhardt
2019-08-28 7:10 ` Patrick Steinhardt [this message]
2019-08-28 7:10 ` [PATCH 6/6] mountd: Use unsigned for filesystem type magic constants Patrick Steinhardt
2019-09-05 12:07 ` [PATCH 0/6] Fixes for various compiler warnings 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=c4efa52412e2ff0e9079bf88ab94d8e366bf8f8f.1566976047.git.ps@pks.im \
--to=ps@pks.im \
--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).