From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] mac80211: mlme: Handle Puncturing information received from the AP
Date: Sat, 26 Mar 2022 01:58:07 +0800 [thread overview]
Message-ID: <202203260107.bl4oXnRb-lkp@intel.com> (raw)
In-Reply-To: <20220325140859.e48bf244f157.I3547481d49f958389f59dfeba3fcc75e72b0aa6e@changeid>
Hi Johannes,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on wireless-next/main]
[also build test ERROR on wireless/main next-20220325]
[cannot apply to v5.17]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Johannes-Berg/mac80211-mlme-Handle-Puncturing-information-received-from-the-AP/20220325-210959
base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
config: arm-randconfig-r014-20220325 (https://download.01.org/0day-ci/archive/20220326/202203260107.bl4oXnRb-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 0f6d9501cf49ce02937099350d08f20c4af86f3d)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://github.com/0day-ci/linux/commit/b248fa1a2c7cfef75823796440bf6fdd81090ac2
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Johannes-Berg/mac80211-mlme-Handle-Puncturing-information-received-from-the-AP/20220325-210959
git checkout b248fa1a2c7cfef75823796440bf6fdd81090ac2
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/net/wireless/intersil/p54/ drivers/staging/wfx/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/staging/wfx/main.c:144:22: error: incompatible function pointer types initializing 'void (*)(struct ieee80211_hw *, struct ieee80211_vif *, struct ieee80211_bss_conf *, u64)' (aka 'void (*)(struct ieee80211_hw *, struct ieee80211_vif *, struct ieee80211_bss_conf *, unsigned long long)') with an expression of type 'void (struct ieee80211_hw *, struct ieee80211_vif *, struct ieee80211_bss_conf *, u32)' (aka 'void (struct ieee80211_hw *, struct ieee80211_vif *, struct ieee80211_bss_conf *, unsigned int)') [-Werror,-Wincompatible-function-pointer-types]
.bss_info_changed = wfx_bss_info_changed,
^~~~~~~~~~~~~~~~~~~~
1 error generated.
--
>> drivers/net/wireless/intersil/p54/main.c:718:22: error: incompatible function pointer types initializing 'void (*)(struct ieee80211_hw *, struct ieee80211_vif *, struct ieee80211_bss_conf *, u64)' (aka 'void (*)(struct ieee80211_hw *, struct ieee80211_vif *, struct ieee80211_bss_conf *, unsigned long long)') with an expression of type 'void (struct ieee80211_hw *, struct ieee80211_vif *, struct ieee80211_bss_conf *, u32)' (aka 'void (struct ieee80211_hw *, struct ieee80211_vif *, struct ieee80211_bss_conf *, unsigned int)') [-Werror,-Wincompatible-function-pointer-types]
.bss_info_changed = p54_bss_info_changed,
^~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +144 drivers/staging/wfx/main.c
40115bbc40e2fd Jérôme Pouiller 2019-09-19 123
e16e7f0716a6ba Jérôme Pouiller 2019-09-19 124 static const struct ieee80211_ops wfx_ops = {
e16e7f0716a6ba Jérôme Pouiller 2019-09-19 125 .start = wfx_start,
e16e7f0716a6ba Jérôme Pouiller 2019-09-19 126 .stop = wfx_stop,
e16e7f0716a6ba Jérôme Pouiller 2019-09-19 127 .add_interface = wfx_add_interface,
e16e7f0716a6ba Jérôme Pouiller 2019-09-19 128 .remove_interface = wfx_remove_interface,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 129 .config = wfx_config,
9bca45f3d6924f Jérôme Pouiller 2019-09-19 130 .tx = wfx_tx,
e836ad4e2da4c4 Jérôme Pouiller 2020-04-10 131 .join_ibss = wfx_join_ibss,
e836ad4e2da4c4 Jérôme Pouiller 2020-04-10 132 .leave_ibss = wfx_leave_ibss,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 133 .conf_tx = wfx_conf_tx,
1a61af0f8cbecd Jérôme Pouiller 2019-09-19 134 .hw_scan = wfx_hw_scan,
4337074be76d85 Jérôme Pouiller 2019-12-17 135 .cancel_hw_scan = wfx_cancel_hw_scan,
cba1d8976db003 Jérôme Pouiller 2020-04-10 136 .start_ap = wfx_start_ap,
cba1d8976db003 Jérôme Pouiller 2020-04-10 137 .stop_ap = wfx_stop_ap,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 138 .sta_add = wfx_sta_add,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 139 .sta_remove = wfx_sta_remove,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 140 .set_tim = wfx_set_tim,
fb2490f693ee01 Jérôme Pouiller 2019-09-19 141 .set_key = wfx_set_key,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 142 .set_rts_threshold = wfx_set_rts_threshold,
7a44644c9379eb Jérôme Pouiller 2020-04-20 143 .set_default_unicast_key = wfx_set_default_unicast_key,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 @144 .bss_info_changed = wfx_bss_info_changed,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 145 .configure_filter = wfx_configure_filter,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 146 .ampdu_action = wfx_ampdu_action,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 147 .flush = wfx_flush,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 148 .add_chanctx = wfx_add_chanctx,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 149 .remove_chanctx = wfx_remove_chanctx,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 150 .change_chanctx = wfx_change_chanctx,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 151 .assign_vif_chanctx = wfx_assign_vif_chanctx,
40115bbc40e2fd Jérôme Pouiller 2019-09-19 152 .unassign_vif_chanctx = wfx_unassign_vif_chanctx,
e16e7f0716a6ba Jérôme Pouiller 2019-09-19 153 };
e16e7f0716a6ba Jérôme Pouiller 2019-09-19 154
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next parent reply other threads:[~2022-03-25 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220325140859.e48bf244f157.I3547481d49f958389f59dfeba3fcc75e72b0aa6e@changeid>
2022-03-25 17:58 ` kernel test robot [this message]
2022-03-25 18:28 ` [RFC PATCH] mac80211: mlme: Handle Puncturing information received from the AP kernel test robot
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=202203260107.bl4oXnRb-lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
/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