linux-kernel - [PATCH] mbxfb: unbreak compilation with CONFIG_FB_MBX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 14 May 2012 18:31:51 +0200
From:	tartler@...fau.de
To:	Florian Tobias Schandinat <FlorianSchandinat@....de>,
	Eric Miao <eric.y.miao@...il.com>,
	Arnd Bergmann <arnd@...db.de>, linux-fbdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Cc:	vamos-dev@...ts.cs.fau.de, Reinhard Tartler <siretart@...ware.de>,
	Reinhard Tartler <tartler@...fau.de>
Subject: [PATCH] mbxfb: unbreak compilation with CONFIG_FB_MBX_DEBUG

From: Reinhard Tartler <siretart@...ware.de>

This patch adds missing function prototypes.

Signed-off-by: Reinhard Tartler <tartler@...fau.de>
---
 drivers/video/mbx/mbxfb.c |    3 +++
 1 file changed, 3 insertions(+)

This patch was found with tools developed in the VAMOS project:
http://www4.cs.fau.de/Research/VAMOS/

TBH, I'm not sure if this is the correct solution. However, I'd
appreciate if someone could confirm that this is a real bug.


diff --git a/drivers/video/mbx/mbxfb.c b/drivers/video/mbx/mbxfb.c
index 6ce3416..c2200ec 100644
--- a/drivers/video/mbx/mbxfb.c
+++ b/drivers/video/mbx/mbxfb.c
@@ -878,6 +878,9 @@ static int mbxfb_resume(struct platform_device *dev)
 #ifndef CONFIG_FB_MBX_DEBUG
 #define mbxfb_debugfs_init(x)	do {} while(0)
 #define mbxfb_debugfs_remove(x)	do {} while(0)
+#else
+void mbxfb_debugfs_init(struct fb_info *fbi);
+void mbxfb_debugfs_remove(struct fb_info *fbi);
 #endif
 
 #define res_size(_r) (((_r)->end - (_r)->start) + 1)
-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/