mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Icenowy Zheng <icenowy@outlook.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
	devel@driverdev.osuosl.org, Icenowy Zheng <icenowy@outlook.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: esp8089: add new driver
Date: Sun, 19 Jun 2016 21:19:42 +0800	[thread overview]
Message-ID: <201606192142.G19DCWxw%fengguang.wu@intel.com> (raw)
In-Reply-To: <BLU436-SMTP46405BB440DB05229192A1BC290@phx.gbl>

[-- Attachment #1: Type: text/plain, Size: 2216 bytes --]

Hi,

[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.7-rc3 next-20160617]
[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/Icenowy-Zheng/staging-esp8089-add-new-driver/20160619-182134
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 4.9.0
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=m68k 

All warnings (new ones prefixed by >>):

>> drivers/staging/esp8089/esp_mac80211.c:1377:2: warning: initialization from incompatible pointer type
     .ampdu_action = esp_op_ampdu_action,
     ^
   drivers/staging/esp8089/esp_mac80211.c:1377:2: warning: (near initialization for 'esp_mac80211_ops.ampdu_action')

vim +1377 drivers/staging/esp8089/esp_mac80211.c

  1361		.update_tkip_key = esp_op_update_tkip_key,
  1362		//.sched_scan_start = esp_op_sched_scan_start,
  1363		//.sched_scan_stop = esp_op_sched_scan_stop,
  1364		.set_rts_threshold = esp_op_set_rts_threshold,
  1365		.sta_notify = esp_op_sta_notify,
  1366		.conf_tx = esp_op_conf_tx,
  1367		.change_interface = esp_op_change_interface,
  1368		.get_tsf = esp_op_get_tsf,
  1369		.set_tsf = esp_op_set_tsf,
  1370		.reset_tsf = esp_op_reset_tsf,
  1371		.rfkill_poll = esp_op_rfkill_poll,
  1372	#ifdef HW_SCAN
  1373		.hw_scan = esp_op_hw_scan,
  1374		.remain_on_channel = esp_op_remain_on_channel,
  1375		.cancel_remain_on_channel = esp_op_cancel_remain_on_channel,
  1376	#endif
> 1377		.ampdu_action = esp_op_ampdu_action,
  1378		//.get_survey = esp_op_get_survey,
  1379		.sta_add = esp_op_sta_add,
  1380		.sta_remove = esp_op_sta_remove,
  1381	#ifdef CONFIG_NL80211_TESTMODE
  1382		//CFG80211_TESTMODE_CMD(esp_op_tm_cmd)
  1383	#endif
  1384		.set_bitrate_mask = esp_op_set_bitrate_mask,
  1385		.flush = esp_op_flush,

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 37228 bytes --]

      parent reply	other threads:[~2016-06-19 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BLU436-SMTP46405BB440DB05229192A1BC290@phx.gbl>
2016-06-19 11:18 ` kbuild test robot
2016-06-19 12:06 ` kbuild test robot
2016-06-19 13:19 ` kbuild test robot [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=201606192142.G19DCWxw%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=icenowy@outlook.com \
    --cc=kbuild-all@01.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

all inboxes | Powered by JetHome®