From: kbuild test robot <lkp@intel.com>
To: Jaganath Kanakkassery <jaganath.k.os@gmail.com>
Cc: kbuild-all@01.org, linux-bluetooth@vger.kernel.org,
Jaganath Kanakkassery <jaganathx.kanakkassery@intel.com>
Subject: Re: [PATCH v1 16/18] Bluetooth: Use ext adv for directed adv
Date: Fri, 13 Apr 2018 22:29:11 +0800 [thread overview]
Message-ID: <201804132258.WzVQyRsH%fengguang.wu@intel.com> (raw)
In-Reply-To: <1523531987-17140-17-git-send-email-jaganathx.kanakkassery@intel.com>
Hi Jaganath,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bluetooth-next/master]
[also build test WARNING on v4.16 next-20180413]
[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/Jaganath-Kanakkassery/Extended-Adv-Scan-Connection-and-PHY-support/20180413-201735
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> net/bluetooth/hci_conn.c:868:35: sparse: incorrect type in assignment (different base types) @@ expected restricted __le16 [addressable] [usertype] evt_properties @@ got e] evt_properties @@
net/bluetooth/hci_conn.c:868:35: expected restricted __le16 [addressable] [usertype] evt_properties
net/bluetooth/hci_conn.c:868:35: got int
vim +868 net/bluetooth/hci_conn.c
855
856 static void hci_req_directed_advertising(struct hci_request *req,
857 struct hci_conn *conn)
858 {
859 struct hci_dev *hdev = req->hdev;
860 u8 own_addr_type;
861 u8 enable;
862
863 if (ext_adv_capable(hdev)) {
864 struct hci_cp_le_set_ext_adv_params cp;
865
866 memset(&cp, 0, sizeof(cp));
867
> 868 cp.evt_properties = LE_LEGACY_ADV_DIRECT_IND;
869 cp.own_addr_type = own_addr_type;
870 cp.channel_map = hdev->le_adv_channel_map;
871 cp.tx_power = 127;
872 cp.primary_phy = HCI_ADV_PHY_1M;
873 cp.secondary_phy = HCI_ADV_PHY_1M;
874 cp.handle = 0; /* Use instance 0 for directed adv */
875 cp.own_addr_type = own_addr_type;
876 cp.peer_addr_type = conn->dst_type;
877 bacpy(&cp.peer_addr, &conn->dst);
878
879 hci_req_add(req, HCI_OP_LE_SET_EXT_ADV_PARAMS, sizeof(cp), &cp);
880
881 __hci_req_enable_ext_advertising(req);
882 } else {
883 struct hci_cp_le_set_adv_param cp;
884
885 /* Clear the HCI_LE_ADV bit temporarily so that the
886 * hci_update_random_address knows that it's safe to go ahead
887 * and write a new random address. The flag will be set back on
888 * as soon as the SET_ADV_ENABLE HCI command completes.
889 */
890 hci_dev_clear_flag(hdev, HCI_LE_ADV);
891
892 /* Set require_privacy to false so that the remote device has a
893 * chance of identifying us.
894 */
895 if (hci_update_random_address(req, false, conn_use_rpa(conn),
896 &own_addr_type) < 0)
897 return;
898
899 memset(&cp, 0, sizeof(cp));
900 cp.type = LE_ADV_DIRECT_IND;
901 cp.own_address_type = own_addr_type;
902 cp.direct_addr_type = conn->dst_type;
903 bacpy(&cp.direct_addr, &conn->dst);
904 cp.channel_map = hdev->le_adv_channel_map;
905
906 hci_req_add(req, HCI_OP_LE_SET_ADV_PARAM, sizeof(cp), &cp);
907
908 enable = 0x01;
909 hci_req_add(req, HCI_OP_LE_SET_ADV_ENABLE, sizeof(enable),
910 &enable);
911 }
912
913 conn->state = BT_CONNECT;
914 }
915
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-04-13 14:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 11:19 [PATCH v1 00/18] Extended Adv, Scan, Connection and PHY support Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 01/18] Bluetooth: Introduce helpers for LE set scan start and complete Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 02/18] Bluetooth: Use extended scanning if controller supports Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 03/18] Bluetooth: Process extended ADV report event Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 04/18] Bluetooth: Introduce helpers for le conn status and complete Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 05/18] Bluetooth: Use extended LE Connection if supported Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 06/18] Bluetooth: Define PHY flags in hdev and set 1M as default Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 07/18] Bluetooth: Implement Get PHY Configuration mgmt command Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 08/18] Bluetooth: Implement Set PHY Confguration command Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 09/18] Bluetooth: Set Scan PHYs based on selected PHYs by user Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 10/18] Bluetooth: Handle extended ADV PDU types Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 11/18] Bluetooth: Use selected PHYs in extended connect Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 12/18] Bluetooth: Read no of adv sets during init Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 13/18] Bluetooth: Impmlement extended adv enable Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 14/18] Bluetooth: Use Set ext adv/scan rsp data if controller supports Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 15/18] Bluetooth: Implement disable and removal of adv instance Jaganath Kanakkassery
2018-04-13 16:28 ` kbuild test robot
2018-04-13 16:28 ` [RFC PATCH] Bluetooth: __hci_req_remove_ext_adv_set() can be static kbuild test robot
2018-04-12 11:19 ` [PATCH v1 16/18] Bluetooth: Use ext adv for directed adv Jaganath Kanakkassery
2018-04-13 14:29 ` kbuild test robot [this message]
2018-04-12 11:19 ` [PATCH v1 17/18] Bluetooth: Implement Set ADV set random address Jaganath Kanakkassery
2018-04-12 11:19 ` [PATCH v1 18/18] Bluetooth: Implement secondary advertising on different PHYs Jaganath Kanakkassery
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=201804132258.WzVQyRsH%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jaganath.k.os@gmail.com \
--cc=jaganathx.kanakkassery@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-bluetooth@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 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.