linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kiran K <kiran.k@intel.com>, linux-bluetooth@vger.kernel.org
Cc: kbuild-all@lists.01.org, ravishankar.srivatsa@intel.com,
	chethan.tumkur.narayan@intel.com, luiz.von.dentz@intel.com,
	Kiran K <kiran.k@intel.com>
Subject: Re: [PATCH v3 10/13] Bluetooth: Handle MSFT avdtp open event
Date: Tue, 16 Nov 2021 01:53:12 +0800	[thread overview]
Message-ID: <202111160128.HHUQhTjS-lkp@intel.com> (raw)
In-Reply-To: <20211115064914.2345-10-kiran.k@intel.com>

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

Hi Kiran,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on bluetooth-next/master]
[also build test WARNING on v5.16-rc1 next-20211115]
[cannot apply to bluetooth/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Kiran-K/Bluetooth-Refactor-code-to-read-supported-codecs-in-getsockopt/20211115-144640
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
config: h8300-randconfig-s031-20211115 (attached as .config)
compiler: h8300-linux-gcc (GCC) 11.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://github.com/0day-ci/linux/commit/0a4eb6e6849d95c7565face4fc18ef652bacad11
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Kiran-K/Bluetooth-Refactor-code-to-read-supported-codecs-in-getsockopt/20211115-144640
        git checkout 0a4eb6e6849d95c7565face4fc18ef652bacad11
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=h8300 

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


sparse warnings: (new ones prefixed by >>)
>> net/bluetooth/hci_event.c:1470:38: sparse: sparse: incorrect type in argument 2 (different base types) @@     expected unsigned short [usertype] dcid @@     got restricted __le16 [usertype] dcid @@
   net/bluetooth/hci_event.c:1470:38: sparse:     expected unsigned short [usertype] dcid
   net/bluetooth/hci_event.c:1470:38: sparse:     got restricted __le16 [usertype] dcid

vim +1470 net/bluetooth/hci_event.c

  1447	
  1448	static void hci_cc_msft_avdtp_open(struct hci_dev *hdev, struct sk_buff *skb)
  1449	{
  1450		struct msft_rp_avdtp_open *rp;
  1451		struct msft_cp_avdtp_open *sent;
  1452		struct hci_conn *hconn;
  1453		struct l2cap_conn *conn;
  1454	
  1455		if (skb->len < sizeof(*rp))
  1456			return;
  1457	
  1458		rp = (void *)skb->data;
  1459	
  1460		sent = hci_sent_cmd_data(hdev, HCI_MSFT_AVDTP_CMD);
  1461	
  1462		hconn = hci_conn_hash_lookup_handle(hdev, __le16_to_cpu(sent->handle));
  1463	
  1464		if (!hconn)
  1465			return;
  1466	
  1467		conn = hconn->l2cap_data;
  1468	
  1469		/* wake up the task waiting on avdtp handle */
> 1470		l2cap_avdtp_wakeup(conn, sent->dcid, rp->status,
  1471				   rp->status ? 0 : __le16_to_cpu(rp->avdtp_handle));
  1472	}
  1473	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30308 bytes --]

  reply	other threads:[~2021-11-15 18:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  6:49 [PATCH v3 01/13] Bluetooth: Refactor code to read supported codecs in getsockopt Kiran K
2021-11-15  6:49 ` [PATCH v3 02/13] Bluetooth: Support reading of codecs supported over l2cap socket Kiran K
2021-11-15  6:49 ` [PATCH v3 03/13] Bluetooth: btintel: cache offload use case data Kiran K
2021-11-15  6:49 ` [PATCH v3 04/13] Bluetooth: Pass transport type in get_data_path_id Kiran K
2021-11-15  6:49 ` [PATCH v3 05/13] Bluetooth: btintel: Add support to fetch data path id for a2dp offload Kiran K
2021-11-15  6:49 ` [PATCH v3 06/13] Bluetooth: Remove unused member in struct hci_vnd_codec_v2 Kiran K
2021-11-15  6:49 ` [PATCH v3 07/13] Bluetooth: Read Output codec capabilities Kiran K
2021-11-15  6:49 ` [PATCH v3 08/13] Bluetooth: Implement MSFT avdtp open command Kiran K
2021-11-15 21:23   ` Luiz Augusto von Dentz
2021-11-19  8:11     ` K, Kiran
2021-11-19 14:27   ` Dan Carpenter
2021-11-15  6:49 ` [PATCH v3 09/13] Bluetooth: Handle MSFT avdtp open event Kiran K
2021-11-15  6:49 ` [PATCH v3 10/13] " Kiran K
2021-11-15 17:53   ` kernel test robot [this message]
2021-11-15  6:49 ` [PATCH v3 11/13] Bluetooth: Implment MSFT avdtp start command Kiran K
2021-11-15  6:49 ` [PATCH v3 12/13] Bluetooth: Implment MSFT avdtp suspend command Kiran K
2021-11-15  6:49 ` [PATCH v3 13/13] Bluetooth: Implment MSFT avdtp close command Kiran K

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=202111160128.HHUQhTjS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.von.dentz@intel.com \
    --cc=ravishankar.srivatsa@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;
as well as URLs for NNTP newsgroup(s).