From: kernel test robot <lkp@intel.com>
To: Kiran K <kiran.k@intel.com>, linux-bluetooth@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com,
chandrashekar.devegowda@intel.com, vijay.satija@intel.com,
Kiran K <kiran.k@intel.com>
Subject: Re: [PATCH v2] Bluetooth: btintel: Allow lowering of drive strength of BRI
Date: Wed, 26 Jun 2024 06:40:41 +0800 [thread overview]
Message-ID: <202406260659.fzB4yn3X-lkp@intel.com> (raw)
In-Reply-To: <20240621064419.2185652-1-kiran.k@intel.com>
Hi Kiran,
kernel test robot noticed the following build errors:
[auto build test ERROR on bluetooth-next/master]
[also build test ERROR on next-20240625]
[cannot apply to bluetooth/master linus/master v6.10-rc5]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Kiran-K/Bluetooth-btintel-Allow-lowering-of-drive-strength-of-BRI/20240625-161151
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
patch link: https://lore.kernel.org/r/20240621064419.2185652-1-kiran.k%40intel.com
patch subject: [PATCH v2] Bluetooth: btintel: Allow lowering of drive strength of BRI
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240626/202406260659.fzB4yn3X-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240626/202406260659.fzB4yn3X-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202406260659.fzB4yn3X-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/bluetooth/btintel.c: In function 'btintel_uefi_get_variable':
>> drivers/bluetooth/btintel.c:66:53: error: passing argument 4 of 'efi.get_variable' from incompatible pointer type [-Werror=incompatible-pointer-types]
66 | status = efi.get_variable(name, guid, NULL, &data_size, NULL);
| ^~~~~~~~~~
| |
| size_t * {aka unsigned int *}
drivers/bluetooth/btintel.c:66:53: note: expected 'long unsigned int *' but argument is of type 'size_t *' {aka 'unsigned int *'}
drivers/bluetooth/btintel.c:76:53: error: passing argument 4 of 'efi.get_variable' from incompatible pointer type [-Werror=incompatible-pointer-types]
76 | status = efi.get_variable(name, guid, NULL, &data_size, data);
| ^~~~~~~~~~
| |
| size_t * {aka unsigned int *}
drivers/bluetooth/btintel.c:76:53: note: expected 'long unsigned int *' but argument is of type 'size_t *' {aka 'unsigned int *'}
cc1: some warnings being treated as errors
vim +66 drivers/bluetooth/btintel.c
49
50 static const guid_t btintel_guid_dsm =
51 GUID_INIT(0xaa10f4e0, 0x81ac, 0x4233,
52 0xab, 0xf6, 0x3b, 0x2a, 0xc5, 0x0e, 0x28, 0xd9);
53
54 static void *btintel_uefi_get_variable(efi_char16_t *name, efi_guid_t *guid)
55 {
56 void *data;
57 efi_status_t status;
58 size_t data_size = 0;
59
60 if (!IS_ENABLED(CONFIG_EFI))
61 return ERR_PTR(-EOPNOTSUPP);
62
63 if (!efi_rt_services_supported(EFI_RT_SUPPORTED_GET_VARIABLE))
64 return ERR_PTR(-EOPNOTSUPP);
65
> 66 status = efi.get_variable(name, guid, NULL, &data_size, NULL);
67
68 if (status != EFI_BUFFER_TOO_SMALL || !data_size)
69 return ERR_PTR(-EIO);
70
71 data = kmalloc(data_size, GFP_KERNEL);
72
73 if (!data)
74 return ERR_PTR(-ENOMEM);
75
76 status = efi.get_variable(name, guid, NULL, &data_size, data);
77
78 if (status != EFI_SUCCESS) {
79 kfree(data);
80 return ERR_PTR(-ENXIO);
81 }
82
83 return data;
84 }
85
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-06-25 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 6:44 [PATCH v2] Bluetooth: btintel: Allow lowering of drive strength of BRI Kiran K
2024-06-21 7:16 ` Paul Menzel
2024-06-24 8:09 ` K, Kiran
2024-06-25 22:40 ` kernel test robot [this message]
2024-06-26 0:19 ` kernel 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=202406260659.fzB4yn3X-lkp@intel.com \
--to=lkp@intel.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ravishankar.srivatsa@intel.com \
--cc=vijay.satija@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