From: Thomas Zimmermann <tzimmermann@suse.de>
To: deller@gmx.de, David.Laight@ACULAB.COM
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-sh@vger.kernel.org, Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH 1/3] fbdev/hitfb: Declare hitfb_blank() as static
Date: Tue, 6 Jun 2023 12:40:54 +0200 [thread overview]
Message-ID: <20230606104056.29553-2-tzimmermann@suse.de> (raw)
In-Reply-To: <20230606104056.29553-1-tzimmermann@suse.de>
Fixes the following warnings:
../drivers/video/fbdev/hitfb.c:186:5: warning: no previous prototype for 'hitfb_blank' [-Wmissing-prototypes]
186 | int hitfb_blank(int blank_mode, struct fb_info *info)
| ^~~~~~~~~~~
../drivers/video/fbdev/hitfb.c:186:5: warning: symbol 'hitfb_blank' was not declared. Should it be static?
Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
---
drivers/video/fbdev/hitfb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/hitfb.c b/drivers/video/fbdev/hitfb.c
index fb82869283db..551b00f761a7 100644
--- a/drivers/video/fbdev/hitfb.c
+++ b/drivers/video/fbdev/hitfb.c
@@ -183,7 +183,7 @@ static int hitfb_pan_display(struct fb_var_screeninfo *var,
return 0;
}
-int hitfb_blank(int blank_mode, struct fb_info *info)
+static int hitfb_blank(int blank_mode, struct fb_info *info)
{
unsigned short v;
--
2.40.1
next prev parent reply other threads:[~2023-06-06 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 10:40 [PATCH 0/3] fbdev/hitfb: Various fixes Thomas Zimmermann
2023-06-06 10:40 ` Thomas Zimmermann [this message]
2023-06-06 10:40 ` [PATCH 2/3] fbdev/hitfb: Fix integer-to-pointer cast Thomas Zimmermann
2023-06-06 10:40 ` [PATCH 3/3] fbdev/hitfb: Use NULL for pointers Thomas Zimmermann
2023-06-06 12:35 ` [PATCH 0/3] fbdev/hitfb: Various fixes Ruhl, Michael J
2023-06-12 14:59 ` Thomas Zimmermann
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=20230606104056.29553-2-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=David.Laight@ACULAB.COM \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-sh@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).