linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Govind Singh <govinds@codeaurora.org>
Cc: kbuild-all@01.org, andy.gross@linaro.org,
	bjorn.andersson@linaro.org, david.brown@linaro.org,
	linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
	Govind Singh <govinds@codeaurora.org>
Subject: Re: [PATCH v2 6/6] ath10k: Add QMI message handshake for wcn3990 client
Date: Wed, 6 Jun 2018 13:34:34 +0800	[thread overview]
Message-ID: <201806061345.vjqQKeNS%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180605123732.1993-1-govinds@codeaurora.org>

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

Hi Govind,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on ath6kl/ath-next]
[also build test WARNING on next-20180605]
[cannot apply to v4.17]
[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/Govind-Singh/Add-support-for-wifi-QMI-client-driver/20180606-064401
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath-next
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/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=arm 

All warnings (new ones prefixed by >>):

   drivers/net/wireless/ath/ath10k/qmi.c: In function 'ath10k_qmi_msa_mem_info_send_sync_msg':
>> drivers/net/wireless/ath/ath10k/qmi.c:169:61: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 5 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
      ath10k_dbg(ar, ATH10K_DBG_QMI, "mem region: %d Addr: 0x%llx Size: 0x%x Flag: 0x%08x\n",
                                                             ~~~^
                                                             %x
          i, qmi->mem_region[i].addr,
             ~~~~~~~~~~~~~~~~~~~~~~~                             

vim +169 drivers/net/wireless/ath/ath10k/qmi.c

   119	
   120	static int ath10k_qmi_msa_mem_info_send_sync_msg(struct ath10k_qmi *qmi)
   121	{
   122		struct wlfw_msa_info_resp_msg_v01 resp = {};
   123		struct wlfw_msa_info_req_msg_v01 req = {};
   124		struct ath10k *ar = qmi->ar;
   125		struct qmi_txn txn;
   126		int ret;
   127		int i;
   128	
   129		req.msa_addr = qmi->msa_pa;
   130		req.size = qmi->msa_mem_size;
   131	
   132		ret = qmi_txn_init(&qmi->qmi_hdl, &txn,
   133				   wlfw_msa_info_resp_msg_v01_ei, &resp);
   134		if (ret < 0)
   135			goto out;
   136	
   137		ret = qmi_send_request(&qmi->qmi_hdl, NULL, &txn,
   138				       QMI_WLFW_MSA_INFO_REQ_V01,
   139				       WLFW_MSA_INFO_REQ_MSG_V01_MAX_MSG_LEN,
   140				       wlfw_msa_info_req_msg_v01_ei, &req);
   141		if (ret < 0) {
   142			qmi_txn_cancel(&txn);
   143			ath10k_err(ar, "fail to send msa mem info req %d\n", ret);
   144			goto out;
   145		}
   146	
   147		ret = qmi_txn_wait(&txn, WLFW_TIMEOUT * HZ);
   148		if (ret < 0)
   149			goto out;
   150	
   151		if (resp.resp.result != QMI_RESULT_SUCCESS_V01) {
   152			ath10k_err(ar, "msa info req rejected, err:%d\n", resp.resp.error);
   153			ret = -EINVAL;
   154			goto out;
   155		}
   156	
   157		if (resp.mem_region_info_len > QMI_WLFW_MAX_MEM_REG_V01) {
   158			ath10k_err(ar, "invalid memory region length received: %d\n",
   159				   resp.mem_region_info_len);
   160			ret = -EINVAL;
   161			goto out;
   162		}
   163	
   164		qmi->nr_mem_region = resp.mem_region_info_len;
   165		for (i = 0; i < resp.mem_region_info_len; i++) {
   166			qmi->mem_region[i].addr = resp.mem_region_info[i].region_addr;
   167			qmi->mem_region[i].size = resp.mem_region_info[i].size;
   168			qmi->mem_region[i].secure = resp.mem_region_info[i].secure_flag;
 > 169			ath10k_dbg(ar, ATH10K_DBG_QMI, "mem region: %d Addr: 0x%llx Size: 0x%x Flag: 0x%08x\n",
   170				   i, qmi->mem_region[i].addr,
   171				   qmi->mem_region[i].size,
   172				   qmi->mem_region[i].secure);
   173		}
   174	
   175		ath10k_dbg(ar, ATH10K_DBG_QMI, "msa mem info request completed\n");
   176		return 0;
   177	
   178	out:
   179		return ret;
   180	}
   181	

---
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: 65292 bytes --]

  parent reply	other threads:[~2018-06-06  5:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 12:37 [PATCH v2 6/6] ath10k: Add QMI message handshake for wcn3990 client Govind Singh
2018-06-05 23:25 ` Brian Norris
2018-06-08 12:07   ` Govind Singh
2018-06-08 12:09   ` Govind Singh
2018-06-06  5:34 ` kbuild test robot [this message]
2018-06-15 13:14 ` Kalle Valo
2018-06-19 22:51 ` Niklas Cassel
2018-07-03 15:15   ` Kalle Valo
2018-07-06  9:18     ` Govind Singh
2018-07-06  9:40   ` Govind Singh
2018-07-03 17:57 ` Kalle Valo
2018-07-03 18:06 ` Kalle Valo
2018-07-06  9:24   ` Govind Singh

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=201806061345.vjqQKeNS%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=andy.gross@linaro.org \
    --cc=ath10k@lists.infradead.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=govinds@codeaurora.org \
    --cc=kbuild-all@01.org \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).