From: kernel test robot <lkp@intel.com>
To: Brian Gix <brian.gix@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Subject: [linux-next:master 4824/6679] net/bluetooth/mgmt.c:4398:6-13: WARNING: kzalloc should be used for rp, instead of kmalloc/memset
Date: Mon, 12 Sep 2022 19:47:20 +0800 [thread overview]
Message-ID: <202209121920.LcZ6ipvg-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 044b771be9c5de9d817dfafb829d2f049c71c3b4
commit: af6bcc1921ff0b644d2d750c0e3a88623b7211f5 [4824/6679] Bluetooth: Add experimental wrapper for MGMT based mesh
config: arm-randconfig-c034-20220911 (https://download.01.org/0day-ci/archive/20220912/202209121920.LcZ6ipvg-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.1.0
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
cocci warnings: (new ones prefixed by >>)
>> net/bluetooth/mgmt.c:4398:6-13: WARNING: kzalloc should be used for rp, instead of kmalloc/memset
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-12 11:47 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=202209121920.LcZ6ipvg-lkp@intel.com \
--to=lkp@intel.com \
--cc=brian.gix@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=luiz.von.dentz@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