From: Matthias Kaehlcke <mka@chromium.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Balakrishna Godavarthi <bgodavar@codeaurora.org>,
Harish Bandi <c-hbandi@codeaurora.org>,
Rocky Liao <rjliao@codeaurora.org>
Subject: Re: [PATCH v8] Bluetooth: btqca: inject command complete event during fw download
Date: Tue, 30 Apr 2019 08:38:11 -0700 [thread overview]
Message-ID: <20190430153811.GK112750@google.com> (raw)
In-Reply-To: <201904301409.dhHyM2xm%lkp@intel.com>
On Tue, Apr 30, 2019 at 02:27:33PM +0800, kbuild test robot wrote:
> Hi Matthias,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on bluetooth-next/master]
> [also build test ERROR on next-20190429]
> [cannot apply to v5.1-rc7]
> [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/Matthias-Kaehlcke/Bluetooth-btqca-inject-command-complete-event-during-fw-download/20190430-125407
> base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
> config: xtensa-allyesconfig (attached as .config)
> compiler: xtensa-linux-gcc (GCC) 8.1.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
> GCC_VERSION=8.1.0 make.cross ARCH=xtensa
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> drivers/bluetooth/btqca.c: In function 'qca_inject_cmd_complete_event':
> >> drivers/bluetooth/btqca.c:286:18: error: 'QCA_HCI_CC_SUCCESS' undeclared (first use in this function); did you mean 'QCA_HCI_CC_OPCODE'?
> skb_put_u8(skb, QCA_HCI_CC_SUCCESS);
> ^~~~~~~~~~~~~~~~~~
> QCA_HCI_CC_OPCODE
> drivers/bluetooth/btqca.c:286:18: note: each undeclared identifier is reported only once for each function it appears in
>
> vim +286 drivers/bluetooth/btqca.c
>
> 267
> 268 static int qca_inject_cmd_complete_event(struct hci_dev *hdev)
> 269 {
> 270 struct hci_event_hdr *hdr;
> 271 struct hci_ev_cmd_complete *evt;
> 272 struct sk_buff *skb;
> 273
> 274 skb = bt_skb_alloc(sizeof(*hdr) + sizeof(*evt) + 1, GFP_KERNEL);
> 275 if (!skb)
> 276 return -ENOMEM;
> 277
> 278 hdr = skb_put(skb, sizeof(*hdr));
> 279 hdr->evt = HCI_EV_CMD_COMPLETE;
> 280 hdr->plen = sizeof(*evt) + 1;
> 281
> 282 evt = skb_put(skb, sizeof(*evt));
> 283 evt->ncmd = 1;
> 284 evt->opcode = HCI_OP_NOP;
> 285
> > 286 skb_put_u8(skb, QCA_HCI_CC_SUCCESS);
Oh, I changed it in my tree, but somehow missed to include this file
in the commit ...
I'll fix it in the next version. Since I expect the change to remain
controversial I'll wait a bit for other comments before sending out
v9.
Thanks
Matthias
next prev parent reply other threads:[~2019-04-30 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 0:10 [PATCH v8] Bluetooth: btqca: inject command complete event during fw download Matthias Kaehlcke
2019-04-30 0:14 ` Matthias Kaehlcke
2019-04-30 6:27 ` kbuild test robot
2019-04-30 15:38 ` Matthias Kaehlcke [this message]
2019-05-01 5:18 ` Balakrishna Godavarthi
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=20190430153811.GK112750@google.com \
--to=mka@chromium.org \
--cc=bgodavar@codeaurora.org \
--cc=c-hbandi@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=marcel@holtmann.org \
--cc=rjliao@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.