From: Baoyou Xie <baoyou.xie@linaro.org>
To: robdclark@gmail.com, airlied@linux.ie, architt@codeaurora.org,
cstout@chromium.org
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
arnd@arndb.de, baoyou.xie@linaro.org, xie.baoyou@zte.com.cn,
han.fei@zte.com.cn, tang.qiang007@zte.com.cn
Subject: [PATCH 1/2] drm/msm: add missing header dependencies
Date: Sat, 22 Oct 2016 17:17:45 +0800 [thread overview]
Message-ID: <1477127865-9381-2-git-send-email-baoyou.xie@linaro.org> (raw)
In-Reply-To: <1477127865-9381-1-git-send-email-baoyou.xie@linaro.org>
We get 2 warnings when building kernel with W=1:
drivers/gpu/drm/msm/msm_debugfs.c:141:5: warning: no previous prototype for 'msm_debugfs_init' [-Wmissing-prototypes]
drivers/gpu/drm/msm/msm_debugfs.c:158:6: warning: no previous prototype for 'msm_debugfs_cleanup' [-Wmissing-prototypes]
In fact, these functions are declared in
drivers/gpu/drm/msm/msm_debugfs.h.
So this patch adds missing header dependencies.
Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
---
drivers/gpu/drm/msm/msm_debugfs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/msm/msm_debugfs.c b/drivers/gpu/drm/msm/msm_debugfs.c
index 663f2b6..3c85373 100644
--- a/drivers/gpu/drm/msm/msm_debugfs.c
+++ b/drivers/gpu/drm/msm/msm_debugfs.c
@@ -18,6 +18,7 @@
#ifdef CONFIG_DEBUG_FS
#include "msm_drv.h"
#include "msm_gpu.h"
+#include "msm_debugfs.h"
static int msm_gpu_show(struct drm_device *dev, struct seq_file *m)
{
--
2.7.4
next prev parent reply other threads:[~2016-10-22 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 9:17 [PATCH 2/2] drm/msm/adreno: move function declarations to header file Baoyou Xie
2016-10-22 9:17 ` Baoyou Xie [this message]
2016-10-24 10:13 ` [PATCH 1/2] drm/msm: add missing header dependencies Arnd Bergmann
2016-10-24 14:31 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2016-09-25 7:51 Baoyou Xie
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=1477127865-9381-2-git-send-email-baoyou.xie@linaro.org \
--to=baoyou.xie@linaro.org \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.org \
--cc=arnd@arndb.de \
--cc=cstout@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=han.fei@zte.com.cn \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=tang.qiang007@zte.com.cn \
--cc=xie.baoyou@zte.com.cn \
/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).