public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hilda Wu <hildawu@realtek.com>, marcel@holtmann.org
Cc: oe-kbuild-all@lists.linux.dev, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	max.chou@realtek.com, alex_lu@realsil.com.cn
Subject: Re: [PATCH v2 1/2] Bluetooth: btrtl: Firmware format v3 support
Date: Tue, 10 Jun 2025 07:12:37 +0800	[thread overview]
Message-ID: <202506100621.JeEJ7e7X-lkp@intel.com> (raw)
In-Reply-To: <20250606090559.896242-2-hildawu@realtek.com>

Hi Hilda,

kernel test robot noticed the following build warnings:

[auto build test WARNING on bluetooth/master]
[also build test WARNING on bluetooth-next/master linus/master v6.16-rc1 next-20250606]
[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/Hilda-Wu/Bluetooth-btrtl-Firmware-format-v3-support/20250606-170957
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git master
patch link:    https://lore.kernel.org/r/20250606090559.896242-2-hildawu%40realtek.com
patch subject: [PATCH v2 1/2] Bluetooth: btrtl: Firmware format v3 support
config: arm-randconfig-r061-20250609 (https://download.01.org/0day-ci/archive/20250610/202506100621.JeEJ7e7X-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0

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/202506100621.JeEJ7e7X-lkp@intel.com/

cocci warnings: (new ones prefixed by >>)
>> drivers/bluetooth/btrtl.c:1676:3-9: WARNING: NULL check before some freeing functions is not needed.
   drivers/bluetooth/btrtl.c:1678:3-9: WARNING: NULL check before some freeing functions is not needed.

vim +1676 drivers/bluetooth/btrtl.c

  1659	
  1660	void btrtl_free(struct btrtl_device_info *btrtl_dev)
  1661	{
  1662		struct rtl_subsection *entry, *tmp;
  1663		struct rtl_section_patch_image *image, *next;
  1664	
  1665		kvfree(btrtl_dev->fw_data);
  1666		kvfree(btrtl_dev->cfg_data);
  1667	
  1668		list_for_each_entry_safe(entry, tmp, &btrtl_dev->patch_subsecs, list) {
  1669			list_del(&entry->list);
  1670			kfree(entry);
  1671		}
  1672	
  1673		list_for_each_entry_safe(image, next, &btrtl_dev->patch_images, list) {
  1674			list_del(&image->list);
  1675			if (image->image_data)
> 1676				kvfree(image->image_data);
  1677			if (image->cfg_buf)
  1678				kvfree(image->cfg_buf);
  1679			kfree(image);
  1680		}
  1681	
  1682		kfree(btrtl_dev);
  1683	}
  1684	EXPORT_SYMBOL_GPL(btrtl_free);
  1685	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-06-09 23:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06  9:05 [PATCH v2 0/2] Bluetooth: Add support for RTK firmware version 3 and enhanced ACL-based download acceleration Hilda Wu
2025-06-06  9:05 ` [PATCH v2 1/2] Bluetooth: btrtl: Firmware format v3 support Hilda Wu
2025-06-06  9:35   ` Bluetooth: Add support for RTK firmware version 3 and enhanced ACL-based download acceleration bluez.test.bot
2025-06-09 23:12   ` kernel test robot [this message]
2025-06-06  9:05 ` [PATCH v2 2/2] Bluetooth: btrtl: Add enhanced download support Hilda Wu
2025-07-02  3:36 ` [PATCH v2 0/2] Bluetooth: Add support for RTK firmware version 3 and enhanced ACL-based download acceleration Hilda Wu
2025-07-02 13:05   ` Luiz Augusto von Dentz

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=202506100621.JeEJ7e7X-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alex_lu@realsil.com.cn \
    --cc=hildawu@realtek.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=max.chou@realtek.com \
    --cc=oe-kbuild-all@lists.linux.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