From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: drivers/pnp/isapnp/core.c:1107:1: warning: no return statement in function returning non-void
Date: Fri, 28 Sep 2012 16:32:16 +0000 [thread overview]
Message-ID: <20120928163216.GA5171@localhost> (raw)
Hi Andy,
FYI, there are new compile warnings show up in
commit: 9b5d971a9c08ba957d9f1e30a58885985736263d UBUNTU: SAUCE: isapnp_init: make isa PNP scans occur async
config: alpha-defconfig
All warnings:
drivers/pnp/isapnp/core.c: In function 'isapnp_init':
drivers/pnp/isapnp/core.c:1107:1: warning: no return statement in function returning non-void [-Wreturn-type]
vim +1107 drivers/pnp/isapnp/core.c
9b5d971a (Andy Whitcroft 2009-12-02 1099) static void __init async_isapnp_init(void *unused, async_cookie_t cookie)
9b5d971a (Andy Whitcroft 2009-12-02 1100) {
9b5d971a (Andy Whitcroft 2009-12-02 1101) (void)real_isapnp_init();
9b5d971a (Andy Whitcroft 2009-12-02 1102) }
9b5d971a (Andy Whitcroft 2009-12-02 1103)
9b5d971a (Andy Whitcroft 2009-12-02 1104) static int __init isapnp_init(void)
9b5d971a (Andy Whitcroft 2009-12-02 1105) {
9b5d971a (Andy Whitcroft 2009-12-02 1106) async_schedule(async_isapnp_init, NULL);
9b5d971a (Andy Whitcroft 2009-12-02 @1107) }
^1da177e (Linus Torvalds 2005-04-16 1108) device_initcall(isapnp_init);
^1da177e (Linus Torvalds 2005-04-16 1109)
^1da177e (Linus Torvalds 2005-04-16 1110) /* format is: noisapnp */
^1da177e (Linus Torvalds 2005-04-16 1111)
^1da177e (Linus Torvalds 2005-04-16 1112) static int __init isapnp_setup_disable(char *str)
^1da177e (Linus Torvalds 2005-04-16 1113) {
^1da177e (Linus Torvalds 2005-04-16 1114) isapnp_disable = 1;
^1da177e (Linus Torvalds 2005-04-16 1115) return 1;
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu, Yuanhan Liu Intel Corporation
reply other threads:[~2012-09-28 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120928163216.GA5171@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