From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [staging:staging-next 93/99] drivers/staging/sm7xxfb/sm7xxfb.c:1061:1: warning: data definition has
Date: Thu, 12 Jul 2012 06:39:36 +0000 [thread overview]
Message-ID: <20120712063936.GA8979@localhost> (raw)
Hi Devendra,
There are new compile warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-next
head: d99b5ac65e7827f10ba60b1ea44d7bd041d58d1d
commit: e6345c81b4eb20850ae4078ed3a8ff6eae584283 [93/99] staging/sm7xxfb: use module_pci_driver macro
All warnings:
drivers/staging/sm7xxfb/sm7xxfb.c:1061:1: warning: data definition has no type or storage class [enabled by default]
drivers/staging/sm7xxfb/sm7xxfb.c:1061:1: warning: type defaults to 'int' in declaration of 'module_pci_driver' [-Wimplicit-int]
drivers/staging/sm7xxfb/sm7xxfb.c:1061:1: warning: parameter names (without types) in function declaration [enabled by default]
drivers/staging/sm7xxfb/sm7xxfb.c:765:19: warning: 'sm712vga_setup' defined but not used [-Wunused-function]
drivers/staging/sm7xxfb/sm7xxfb.c:1053:26: warning: 'smtcfb_driver' defined but not used [-Wunused-variable]
vim +1061 drivers/staging/sm7xxfb/sm7xxfb.c
1058 .driver.pm = SM7XX_PM_OPS,
1059 };
1060
> 1061 module_pci_driver(smtcfb_driver);
1062
1063 MODULE_AUTHOR("Siliconmotion ");
1064 MODULE_DESCRIPTION("Framebuffer driver for SMI Graphic Cards");
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
next reply other threads:[~2012-07-12 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 6:39 Fengguang Wu [this message]
2012-07-12 7:51 ` [staging:staging-next 93/99] drivers/staging/sm7xxfb/sm7xxfb.c:1061:1: warning: data definition devendra.aaru
2012-07-12 8:02 ` Dan Carpenter
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=20120712063936.GA8979@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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