public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sven Peter <sven@svenpeter.dev>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [asahilinux:bluetooth-wip 8/8] drivers/bluetooth/hci_bcm43xx.c:1062:30: warning: unused variable 'bcm43xx'
Date: Fri, 8 Jul 2022 04:08:02 +0800	[thread overview]
Message-ID: <202207080351.QotD6R07-lkp@intel.com> (raw)

tree:   https://github.com/AsahiLinux/linux bluetooth-wip
head:   a1e15829f0faa83ea0884f38fa4cae8990f76801
commit: a1e15829f0faa83ea0884f38fa4cae8990f76801 [8/8] Bluetooth: hci_bcm43xx: Add new driver for BCM43XX PCI boards
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220708/202207080351.QotD6R07-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
        # https://github.com/AsahiLinux/linux/commit/a1e15829f0faa83ea0884f38fa4cae8990f76801
        git remote add asahilinux https://github.com/AsahiLinux/linux
        git fetch --no-tags asahilinux bluetooth-wip
        git checkout a1e15829f0faa83ea0884f38fa4cae8990f76801
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/bluetooth/

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

All warnings (new ones prefixed by >>):

   drivers/bluetooth/hci_bcm43xx.c: In function 'bcm43xx_hci_close':
>> drivers/bluetooth/hci_bcm43xx.c:1062:30: warning: unused variable 'bcm43xx' [-Wunused-variable]
    1062 |         struct bcm43xx_data *bcm43xx = hci_get_drvdata(hdev);
         |                              ^~~~~~~
   drivers/bluetooth/hci_bcm43xx.c: In function 'bcm43xx_init_context':
   drivers/bluetooth/hci_bcm43xx.c:1243:29: error: passing argument 3 of 'dmam_alloc_coherent' from incompatible pointer type [-Werror=incompatible-pointer-types]
    1243 |                             &bcm43xx->ctx->per_info_addr, GFP_KERNEL);
         |                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
         |                             |
         |                             __le64 * {aka long long unsigned int *}
   In file included from drivers/bluetooth/hci_bcm43xx.c:34:
   include/linux/dma-mapping.h:550:29: note: expected 'dma_addr_t *' {aka 'unsigned int *'} but argument is of type '__le64 *' {aka 'long long unsigned int *'}
     550 |                 dma_addr_t *dma_handle, gfp_t gfp)
         |                 ~~~~~~~~~~~~^~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/bcm43xx +1062 drivers/bluetooth/hci_bcm43xx.c

  1059	
  1060	static int bcm43xx_hci_close(struct hci_dev *hdev)
  1061	{
> 1062		struct bcm43xx_data *bcm43xx = hci_get_drvdata(hdev);
  1063	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-07-07 20:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202207080351.QotD6R07-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sven@svenpeter.dev \
    /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