From: tartler@cs.fau.de
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
Eric Miao <eric.y.miao@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: vamos-dev@lists.cs.fau.de, Reinhard Tartler <siretart@tauware.de>,
Reinhard Tartler <tartler@cs.fau.de>
Subject: [PATCH] mbxfb: unbreak compilation with CONFIG_FB_MBX_DEBUG
Date: Mon, 14 May 2012 16:31:51 +0000 [thread overview]
Message-ID: <1337013111-7732-1-git-send-email-tartler@cs.fau.de> (raw)
From: Reinhard Tartler <siretart@tauware.de>
This patch adds missing function prototypes.
Signed-off-by: Reinhard Tartler <tartler@cs.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
next reply other threads:[~2012-05-14 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 16:31 tartler [this message]
2012-05-16 0:20 ` [PATCH] mbxfb: unbreak compilation with CONFIG_FB_MBX_DEBUG Eric Miao
2012-06-05 19:15 ` Florian Tobias Schandinat
2012-06-05 20:54 ` Eric Miao
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=1337013111-7732-1-git-send-email-tartler@cs.fau.de \
--to=tartler@cs.fau.de \
--cc=FlorianSchandinat@gmx.de \
--cc=arnd@arndb.de \
--cc=eric.y.miao@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siretart@tauware.de \
--cc=vamos-dev@lists.cs.fau.de \
/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).