From: Kalle Valo <kvalo@codeaurora.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, ath10k@lists.infradead.org
Subject: Re: [ath6kl:master-pending 3/3] drivers/net/wireless/ath/ath10k/qmi.c:734:44: error: not enough arguments for function ath10k_core_fetch_board_file
Date: Fri, 12 Oct 2018 17:28:12 +0300 [thread overview]
Message-ID: <87tvlr44ub.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <201810112257.Hgqd4vtm%fengguang.wu@intel.com> (kbuild test robot's message of "Thu, 11 Oct 2018 22:31:59 +0800")
kbuild test robot <lkp@intel.com> writes:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git master-pending
> head: 0867465f6a7f45f857c8289a61a7f847829d3654
> commit: 0867465f6a7f45f857c8289a61a7f847829d3654 [3/3] Merge branch 'pending' into master-pending
> config: x86_64-allmodconfig (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> git checkout 0867465f6a7f45f857c8289a61a7f847829d3654
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All error/warnings (new ones prefixed by >>):
>
>>> drivers/net/wireless/ath/ath10k/qmi.c:734:44: error: not enough arguments for function ath10k_core_fetch_board_file
> drivers/net/wireless/ath/ath10k/qmi.c: In function 'ath10k_qmi_fetch_board_file':
> drivers/net/wireless/ath/ath10k/qmi.c:734:9: error: too few arguments to function 'ath10k_core_fetch_board_file'
> return ath10k_core_fetch_board_file(qmi->ar);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> In file included from drivers/net/wireless/ath/ath10k/trace.h:21:0,
> from drivers/net/wireless/ath/ath10k/debug.h:23,
> from drivers/net/wireless/ath/ath10k/qmi.c:31:
> drivers/net/wireless/ath/ath10k/core.h:1224:5: note: declared here
> int ath10k_core_fetch_board_file(struct ath10k *ar, int bd_ie_type);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/net/wireless/ath/ath10k/qmi.c:735:1: warning: control reaches end of non-void function [-Wreturn-type]
> }
> ^
> --
>>> drivers/net/wireless/ath/ath10k/snoc.c:1191:17: error: undefined identifier 'bus_params'
> drivers/net/wireless/ath/ath10k/snoc.c:1192:17: error: undefined identifier 'bus_params'
>>> drivers/net/wireless/ath/ath10k/snoc.c:1192:38: error: undefined identifier 'drv_data'
> drivers/net/wireless/ath/ath10k/snoc.c:1193:49: error: undefined identifier 'bus_params'
>>> drivers/net/wireless/ath/ath10k/snoc.c:1192:46: warning: unknown expression (8 46)
> drivers/net/wireless/ath/ath10k/snoc.c: In function 'ath10k_snoc_fw_indication':
> drivers/net/wireless/ath/ath10k/snoc.c:1191:3: error: 'bus_params' undeclared (first use in this function); did you mean 'key_params'?
> bus_params.dev_type = ATH10K_DEV_TYPE_LL;
> ^~~~~~~~~~
> key_params
> drivers/net/wireless/ath/ath10k/snoc.c:1191:3: note: each undeclared identifier is reported only once for each function it appears in
> drivers/net/wireless/ath/ath10k/snoc.c:1192:24: error: 'drv_data' undeclared (first use in this function); did you mean 'irq_data'?
> bus_params.chip_id = drv_data->hw_rev;
> ^~~~~~~~
> irq_data
> drivers/net/wireless/ath/ath10k/snoc.c:1186:22: warning: unused variable 'ar_snoc' [-Wunused-variable]
> struct ath10k_snoc *ar_snoc = ath10k_snoc_priv(ar);
> ^~~~~~~
> drivers/net/wireless/ath/ath10k/snoc.c: In function 'ath10k_snoc_probe':
> drivers/net/wireless/ath/ath10k/snoc.c:1536:27: warning: unused variable 'bus_params' [-Wunused-variable]
> struct ath10k_bus_params bus_params;
> ^~~~~~~~~~
These errors are my mistakes. I introduced these when solving some
conflicts and not having COMPILE_TEST enabled so I didn't compile check
snoc.c. These should be fixed now in the pending branch.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2018-10-12 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 14:31 [ath6kl:master-pending 3/3] drivers/net/wireless/ath/ath10k/qmi.c:734:44: error: not enough arguments for function ath10k_core_fetch_board_file kbuild test robot
2018-10-12 14:28 ` Kalle Valo [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=87tvlr44ub.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kbuild-all@01.org \
--cc=lkp@intel.com \
/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