From: Eric Biggers <ebiggers@kernel.org>
To: linux-fsdevel@vger.kernel.org, Alexander Viro <viro@zeniv.linux.org.uk>
Subject: [PATCH] fs/direct-io.c: include fs/internal.h for missing prototype
Date: Wed, 29 May 2019 14:21:00 -0700 [thread overview]
Message-ID: <20190529212100.164185-1-ebiggers@kernel.org> (raw)
From: Eric Biggers <ebiggers@google.com>
Include fs/internal.h to address the following 'sparse' warning:
fs/direct-io.c:622:5: warning: symbol 'sb_init_dio_done_wq' was not declared. Should it be static?
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
fs/direct-io.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/direct-io.c b/fs/direct-io.c
index ac7fb19b6ade5..601b402829239 100644
--- a/fs/direct-io.c
+++ b/fs/direct-io.c
@@ -39,6 +39,8 @@
#include <linux/atomic.h>
#include <linux/prefetch.h>
+#include "internal.h"
+
/*
* How many user pages to map in one call to get_user_pages(). This determines
* the size of a structure in the slab cache
--
2.22.0.rc1.257.g3120a18244-goog
next reply other threads:[~2019-05-29 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 21:21 Eric Biggers [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-09 23:45 [PATCH] fs/direct-io.c: include fs/internal.h for missing prototype Eric Biggers
2019-12-13 10:40 ` Jan Kara
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=20190529212100.164185-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).