All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: SpoorthiX K <spoorthix.k@intel.com>
Cc: kbuild-all@01.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] [v5]Add support for LE ping feature
Date: Thu, 25 Apr 2019 20:18:11 +0800	[thread overview]
Message-ID: <201904252044.HeRmtMBa%lkp@intel.com> (raw)
In-Reply-To: <1556093829-11793-1-git-send-email-spoorthix.k@intel.com>

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

Hi SpoorthiX,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on bluetooth-next/master]
[also build test ERROR on v5.1-rc6 next-20190424]
[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/SpoorthiX-K/Add-support-for-LE-ping-feature/20190425-184628
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
config: i386-randconfig-x074-201916 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   net/bluetooth/hci_event.c: In function 'hci_cc_write_auth_payload_timeout':
>> net/bluetooth/hci_event.c:595:11: error: 'HCI_CONN_AUTH_PAYLOAD_TIMEOUT' undeclared (first use in this function); did you mean 'HCI_CONN_AUTH_FAILURE'?
      set_bit(HCI_CONN_AUTH_PAYLOAD_TIMEOUT, &conn->flags);
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              HCI_CONN_AUTH_FAILURE
   net/bluetooth/hci_event.c:595:11: note: each undeclared identifier is reported only once for each function it appears in
   net/bluetooth/hci_event.c: In function 'hci_encrypt_change_evt':
>> net/bluetooth/hci_event.c:3005:54: error: called object is not a function or function pointer
         lmp_ping_capable(hdev) && (hdev->le_features[0] & HCI_LE_PING)
                                   ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~

vim +595 net/bluetooth/hci_event.c

   581	
   582	static void hci_cc_write_auth_payload_timeout(struct hci_dev *hdev,
   583							struct sk_buff *skb)
   584	{
   585		struct hci_rp_write_auth_payload_to *rp = (void *)skb->data;
   586		struct hci_conn *conn;
   587	
   588		BT_DBG("%s status 0x%2.2x", hdev->name, rp->status);
   589		if (rp->status)
   590			return;
   591		hci_dev_lock(hdev);
   592	
   593		conn = hci_conn_hash_lookup_handle(hdev, __le16_to_cpu(rp->handle));
   594		if (conn)
 > 595			set_bit(HCI_CONN_AUTH_PAYLOAD_TIMEOUT, &conn->flags);
   596	
   597		hci_dev_unlock(hdev);
   598	}
   599	

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

  parent reply	other threads:[~2019-04-25 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  8:17 [PATCH] [v5]Add support for LE ping feature SpoorthiX K
2019-04-24  8:11 ` Marcel Holtmann
2019-04-25 12:18 ` kbuild test robot [this message]
2019-04-25 12:25 ` kbuild 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=201904252044.HeRmtMBa%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=spoorthix.k@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 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.