From: kbuild test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH nomadik] drm/panel: nt35510_send_long() can be static
Date: Wed, 4 Dec 2019 01:59:47 +0800 [thread overview]
Message-ID: <20191203175947.myelnvd3vlyrhj46@4978f4969bb8> (raw)
In-Reply-To: <201912040159.hVq7kws6%lkp@intel.com>
Fixes: 40d1110621b1 ("drm/panel: Add driver for Novatek NT35510-based panels")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
panel-novatek-nt35510.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/panel/panel-novatek-nt35510.c b/drivers/gpu/drm/panel/panel-novatek-nt35510.c
index 09447160a7951..045a1e619a31f 100644
--- a/drivers/gpu/drm/panel/panel-novatek-nt35510.c
+++ b/drivers/gpu/drm/panel/panel-novatek-nt35510.c
@@ -382,8 +382,8 @@ static inline struct nt35510 *panel_to_nt35510(struct drm_panel *panel)
#define NT35510_ROTATE_0_SETTING 0x02
#define NT35510_ROTATE_180_SETTING 0x00
-int nt35510_send_long(struct nt35510 *nt, struct mipi_dsi_device *dsi,
- u8 cmd, u8 cmdlen, const u8 *seq)
+static int nt35510_send_long(struct nt35510 *nt, struct mipi_dsi_device *dsi,
+ u8 cmd, u8 cmdlen, const u8 *seq)
{
const u8 *seqp = seq;
int cmdwritten = 0;
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-12-03 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 17:59 [nomadik:ux500-skomer 40/47] drivers/gpu/drm/panel/panel-novatek-nt35510.c:385:5: sparse: sparse: symbol 'nt35510_send_long' was not declared. Should it be static? kbuild test robot
2019-12-03 17:59 ` kbuild test robot [this message]
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=20191203175947.myelnvd3vlyrhj46@4978f4969bb8 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).