From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-fbdev@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: [PATCH v3 5/5] staging: sm750fb: fix build failure
Date: Tue, 10 Mar 2015 08:57:39 +0000 [thread overview]
Message-ID: <1425977139-25285-5-git-send-email-sudipm.mukherjee@gmail.com> (raw)
In-Reply-To: <1425977139-25285-1-git-send-email-sudipm.mukherjee@gmail.com>
for powerpc-allyesconfig build failed with an error of g_option
undeclared. we will get this error on all architecture if MODULE is
not defined. fixed the declaration of g_option.
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
---
v3: new entry in the series, it was not there till v2.
drivers/staging/sm750fb/sm750.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c
index 476dc5c..8c260ee 100644
--- a/drivers/staging/sm750fb/sm750.c
+++ b/drivers/staging/sm750fb/sm750.c
@@ -54,9 +54,7 @@ static const char * g_fbmode[] = {NULL,NULL};
static const char * g_def_fbmode = "800x600-16@60";
static char * g_settings = NULL;
static int g_dualview = 0;
-#ifdef MODULE
static char * g_option = NULL;
-#endif
/* if not use spin_lock,system will die if user load driver
* and immediatly unload driver frequently (dual)*/
--
1.8.1.2
prev parent reply other threads:[~2015-03-10 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 8:57 [PATCH v3 1/5] staging: sm750fb: wrong type for print Sudip Mukherjee
2015-03-10 8:57 ` [PATCH v3 2/5] staging: sm750fb: remove pragma optimize Sudip Mukherjee
2015-03-10 8:57 ` [PATCH v3 3/5] staging: sm750fb: correctly define SM750LE_REVISION_ID Sudip Mukherjee
2015-03-10 8:57 ` [PATCH v3 4/5] staging: sm750fb: fix undeclared function Sudip Mukherjee
2015-03-10 8:57 ` Sudip Mukherjee [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=1425977139-25285-5-git-send-email-sudipm.mukherjee@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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).