From: kbuild test robot <lkp@intel.com>
To: Ashish Kalra <eashishkalra@gmail.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org, wsa@the-dreams.de,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
joe@perches.com, eashishkalra@gmail.com
Subject: Re: [PATCH] staging: ks7010: fix styling WARNINGs
Date: Tue, 1 Aug 2017 12:31:34 +0800 [thread overview]
Message-ID: <201708011234.AjCdofLN%fengguang.wu@intel.com> (raw)
In-Reply-To: <1501470921-1947-1-git-send-email-eashishkalra@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6415 bytes --]
Hi Ashish,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.13-rc3 next-20170731]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Ashish-Kalra/staging-ks7010-fix-styling-WARNINGs/20170801-121331
config: tile-allmodconfig (attached as .config)
compiler: tilegx-linux-gcc (GCC) 4.6.2
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=tile
All errors (new ones prefixed by >>):
drivers/staging//ks7010/ks7010_sdio.c: In function 'ks7010_sdio_readb':
drivers/staging//ks7010/ks7010_sdio.c:77:12: error: invalid storage class for function 'ks7010_sdio_readb'
drivers/staging//ks7010/ks7010_sdio.c:77:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
drivers/staging//ks7010/ks7010_sdio.c:89:12: error: invalid storage class for function 'ks7010_sdio_read'
drivers/staging//ks7010/ks7010_sdio.c:98:12: error: invalid storage class for function 'ks7010_sdio_writeb'
drivers/staging//ks7010/ks7010_sdio.c:110:12: error: invalid storage class for function 'ks7010_sdio_write'
drivers/staging//ks7010/ks7010_sdio.c:118:13: error: invalid storage class for function 'ks_wlan_hw_sleep_doze_request'
drivers/staging//ks7010/ks7010_sdio.c:144:13: error: invalid storage class for function 'ks_wlan_hw_sleep_wakeup_request'
drivers/staging//ks7010/ks7010_sdio.c:191:13: error: invalid storage class for function '_ks_wlan_hw_power_save'
drivers/staging//ks7010/ks7010_sdio.c:252:12: error: invalid storage class for function 'enqueue_txdev'
drivers/staging//ks7010/ks7010_sdio.c:290:12: error: invalid storage class for function 'write_to_device'
drivers/staging//ks7010/ks7010_sdio.c:320:13: error: invalid storage class for function 'tx_device_task'
drivers/staging//ks7010/ks7010_sdio.c:379:13: error: invalid storage class for function 'rx_event_task'
drivers/staging//ks7010/ks7010_sdio.c:396:13: error: invalid storage class for function 'ks_wlan_hw_rx'
drivers/staging//ks7010/ks7010_sdio.c:452:13: error: invalid storage class for function 'ks7010_rw_function'
drivers/staging//ks7010/ks7010_sdio.c:522:13: error: invalid storage class for function 'ks_sdio_interrupt'
drivers/staging//ks7010/ks7010_sdio.c:593:12: error: invalid storage class for function 'trx_device_init'
drivers/staging//ks7010/ks7010_sdio.c:609:13: error: invalid storage class for function 'trx_device_exit'
drivers/staging//ks7010/ks7010_sdio.c:625:12: error: invalid storage class for function 'ks7010_sdio_update_index'
drivers/staging//ks7010/ks7010_sdio.c:652:12: error: invalid storage class for function 'ks7010_sdio_data_compare'
drivers/staging//ks7010/ks7010_sdio.c:680:12: error: invalid storage class for function 'ks7010_upload_firmware'
drivers/staging//ks7010/ks7010_sdio.c:775:13: error: invalid storage class for function 'ks7010_card_init'
drivers/staging//ks7010/ks7010_sdio.c:828:13: error: invalid storage class for function 'ks7010_init_defaults'
drivers/staging//ks7010/ks7010_sdio.c:855:12: error: invalid storage class for function 'ks7010_sdio_probe'
drivers/staging//ks7010/ks7010_sdio.c:1005:12: error: invalid storage class for function 'send_stop_request'
drivers/staging//ks7010/ks7010_sdio.c:1032:13: error: invalid storage class for function 'ks7010_sdio_remove'
drivers/staging//ks7010/ks7010_sdio.c:1100:2: error: initializer element is not constant
drivers/staging//ks7010/ks7010_sdio.c:1100:2: error: (near initialization for 'ks7010_sdio_driver.probe')
drivers/staging//ks7010/ks7010_sdio.c:1101:2: error: initializer element is not constant
drivers/staging//ks7010/ks7010_sdio.c:1101:2: error: (near initialization for 'ks7010_sdio_driver.remove')
drivers/staging//ks7010/ks7010_sdio.c:1104:1: error: invalid storage class for function 'ks7010_sdio_driver_init'
>> drivers/staging//ks7010/ks7010_sdio.c:1104:1: error: invalid storage class for function '__inittest'
drivers/staging//ks7010/ks7010_sdio.c:1104:1: warning: 'alias' attribute ignored [-Wattributes]
drivers/staging//ks7010/ks7010_sdio.c:1104:1: error: invalid storage class for function 'ks7010_sdio_driver_exit'
drivers/staging//ks7010/ks7010_sdio.c:1104:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
>> drivers/staging//ks7010/ks7010_sdio.c:1104:1: error: invalid storage class for function '__exittest'
drivers/staging//ks7010/ks7010_sdio.c:1104:1: warning: 'alias' attribute ignored [-Wattributes]
drivers/staging//ks7010/ks7010_sdio.c:1105:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
drivers/staging//ks7010/ks7010_sdio.c:1108:1: error: expected declaration or statement at end of input
drivers/staging//ks7010/ks7010_sdio.c:1108:1: warning: no return statement in function returning non-void [-Wreturn-type]
drivers/staging//ks7010/ks7010_sdio.c: At top level:
drivers/staging//ks7010/ks7010_sdio.c:69:12: warning: 'ks7010_sdio_readb' defined but not used [-Wunused-function]
vim +/__inittest +1104 drivers/staging//ks7010/ks7010_sdio.c
13a9930d Wolfram Sang 2016-05-31 1096
4c0d46d2 Wolfram Sang 2016-06-17 1097 static struct sdio_driver ks7010_sdio_driver = {
4c0d46d2 Wolfram Sang 2016-06-17 1098 .name = "ks7010_sdio",
4c0d46d2 Wolfram Sang 2016-06-17 1099 .id_table = ks7010_sdio_ids,
4c0d46d2 Wolfram Sang 2016-06-17 @1100 .probe = ks7010_sdio_probe,
4c0d46d2 Wolfram Sang 2016-06-17 1101 .remove = ks7010_sdio_remove,
4c0d46d2 Wolfram Sang 2016-06-17 1102 };
4c0d46d2 Wolfram Sang 2016-06-17 1103
6b0cb0b0 Wolfram Sang 2016-05-31 @1104 module_driver(ks7010_sdio_driver, sdio_register_driver, sdio_unregister_driver);
:::::: The code at line 1104 was first introduced by commit
:::::: 6b0cb0b02ec8c03a16d1bdff4ae79b27874138e1 staging: ks7010: simplify module_init/exit
:::::: TO: Wolfram Sang <wsa+renesas@sang-engineering.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 49807 bytes --]
next prev parent reply other threads:[~2017-08-01 4:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 2:20 [PATCH] Removing Check Errors with checkpatch.pl, Converting from macro to function call Ashish Kalra
2017-08-01 0:25 ` Joe Perches
2017-07-31 3:15 ` [PATCH] staging: ks7010: fix styling WARNINGs Ashish Kalra
2017-08-01 1:18 ` Greg KH
2017-08-01 4:29 ` kbuild test robot
2017-08-01 4:31 ` kbuild test robot [this message]
2017-08-01 16:11 ` Ashish Kalra
2017-08-01 16:22 ` Joe Perches
2017-08-01 17:25 ` [PATCH v2]staging: " Ashish Kalra
2017-08-17 17:58 ` Greg KH
2017-08-01 20:28 ` [PATCH] staging: " Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2017-06-30 4:52 Mark Rogers
2017-06-30 5:54 ` Frans Klaver
2017-06-30 18:39 ` Mark Rogers
2017-07-11 17:27 ` Greg KH
2017-07-12 8:08 ` Frans Klaver
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=201708011234.AjCdofLN%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=eashishkalra@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.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
all inboxes | Powered by JetHome®