From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: thomas@winischhofer.net, adaplas@pol.net, akpm <akpm@osdl.org>
Subject: [PATCH] sis: fix sparse warnings
Date: Wed, 16 Feb 2005 17:14:55 -0800 [thread overview]
Message-ID: <20050216171455.196cb116.rddunlap@osdl.org> (raw)
In-Reply-To: <20050216164142.4f30b90a.rddunlap@osdl.org>
Seeing that Andrew just posted a patch to correct the ioctl
return type, only the include for linux/smp_lock.h is missing.
(Thanks for the message, Thomas.)
sis_main.c needs linux/smp_lock.h;
drivers/video/sis/sis_main.c:2204:2: warning: undefined identifier 'lock_kernel'
drivers/video/sis/sis_main.c:2206:2: warning: undefined identifier 'unlock_kernel'
drivers/video/sis/sis_main.c:2204: warning: implicit declaration of function `lock_kernel'
drivers/video/sis/sis_main.c:2206: warning: implicit declaration of function `unlock_kernel'
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
drivers/video/sis/sis_main.c | 1 +
1 files changed, 1 insertion(+)
diff -Naurp ./drivers/video/sis/sis_main.c~video_sis_includes ./drivers/video/sis/sis_main.c
--- ./drivers/video/sis/sis_main.c~video_sis_includes 2005-02-15 13:48:46.145337888 -0800
+++ ./drivers/video/sis/sis_main.c 2005-02-15 21:25:40.381740480 -0800
@@ -39,6 +39,7 @@
#include <linux/moduleparam.h>
#endif
#include <linux/kernel.h>
+#include <linux/smp_lock.h>
#include <linux/spinlock.h>
#include <linux/errno.h>
#include <linux/string.h>
---
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-02-17 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 0:41 [PATCH] sis: fix sparse warnings Randy.Dunlap
2005-02-17 1:14 ` Randy.Dunlap [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=20050216171455.196cb116.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=thomas@winischhofer.net \
/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).