From: kbuild test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [PATCH v3 31/31] elx: efct: Tie into kernel Kconfig and build process
Date: Sun, 12 Apr 2020 15:22:50 +0800 [thread overview]
Message-ID: <202004121504.E6ItoFUo%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4474 bytes --]
CC: kbuild-all(a)lists.01.org
In-Reply-To: <20200412033303.29574-32-jsmart2021@gmail.com>
References: <20200412033303.29574-32-jsmart2021@gmail.com>
TO: James Smart <jsmart2021@gmail.com>
CC: linux-scsi(a)vger.kernel.org
CC: dwagner(a)suse.de, maier(a)linux.ibm.com, bvanassche(a)acm.org, herbszt(a)gmx.de, natechancellor(a)gmail.com, rdunlap(a)infradead.org, hare(a)suse.de, James Smart <jsmart2021@gmail.com>, Ram Vegesna <ram.vegesna@broadcom.com>
Hi James,
I love your patch! Perhaps something to improve:
[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on scsi/for-next linus/master v5.6 next-20200412]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/James-Smart/efct-Broadcom-Emulex-FC-Target-driver/20200412-114125
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
:::::: branch date: 4 hours ago
:::::: commit date: 4 hours ago
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>
coccinelle warnings: (new ones prefixed by >>)
>> drivers/scsi/elx/efct/efct_hw.c:3897:25-28: ERROR: reference preceded by free on line 3893
drivers/scsi/elx/efct/efct_hw.c:3898:7-10: ERROR: reference preceded by free on line 3893
--
>> drivers/scsi/elx/efct/efct_hw.c:3882:7-14: WARNING: kzalloc should be used for ctx, instead of kmalloc/memset
>> drivers/scsi/elx/efct/efct_hw.c:4509:7-14: WARNING: kzalloc should be used for cmd, instead of kmalloc/memset
>> drivers/scsi/elx/efct/efct_hw.c:4595:7-14: WARNING: kzalloc should be used for buf, instead of kmalloc/memset
>> drivers/scsi/elx/efct/efct_hw.c:5306:11-18: WARNING: kzalloc should be used for mbxdata, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:3484:11-18: WARNING: kzalloc should be used for mbxdata, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:3385:11-18: WARNING: kzalloc should be used for mbxdata, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:5162:11-18: WARNING: kzalloc should be used for mbxdata, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:3122:11-18: WARNING: kzalloc should be used for mbxdata, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:3229:11-18: WARNING: kzalloc should be used for mbxdata, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:4827:7-14: WARNING: kzalloc should be used for buf, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:5003:8-15: WARNING: kzalloc should be used for buf, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:5096:7-14: WARNING: kzalloc should be used for buf, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:4181:8-15: WARNING: kzalloc should be used for cmd, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_hw.c:4263:7-14: WARNING: kzalloc should be used for buf, instead of kmalloc/memset
>> drivers/scsi/elx/efct/efct_hw.c:3977:9-16: WARNING: kzalloc should be used for data, instead of kmalloc/memset
>> drivers/scsi/elx/efct/efct_hw.c:532:18-25: WARNING: kzalloc should be used for hw -> wqe_buffs, instead of kmalloc/memset
--
>> drivers/scsi/elx/efct/efct_hw_queues.c:173:7-14: WARNING: kzalloc should be used for cq, instead of kmalloc/memset
>> drivers/scsi/elx/efct/efct_hw_queues.c:376:7-14: WARNING: kzalloc should be used for rq, instead of kmalloc/memset
--
>> drivers/scsi/elx/efct/efct_lio.c:265:22-29: WARNING: kzalloc should be used for filp -> private_data, instead of kmalloc/memset
drivers/scsi/elx/efct/efct_lio.c:303:22-29: WARNING: kzalloc should be used for filp -> private_data, instead of kmalloc/memset
>> drivers/scsi/elx/efct/efct_lio.c:1462:11-18: WARNING: kzalloc should be used for wq_data, instead of kmalloc/memset
--
>> drivers/scsi/elx/efct/efct_xport.c:44:9-16: WARNING: kzalloc should be used for xport, instead of kmalloc/memset
>> drivers/scsi/elx/efct/efct_xport.c:688:12-19: WARNING: kzalloc should be used for payload, instead of kmalloc/memset
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2020-04-12 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 7:22 kbuild test robot [this message]
2020-04-12 7:22 ` [PATCH] elx: efct: fix zalloc-simple.cocci warnings kbuild test robot
2020-04-12 7:22 ` kbuild test robot
2020-04-12 7:22 ` kbuild test robot
2020-04-12 7:22 ` kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2020-04-12 3:32 [PATCH v3 00/31] [NEW] efct: Broadcom (Emulex) FC Target driver James Smart
2020-04-12 3:33 ` [PATCH v3 31/31] elx: efct: Tie into kernel Kconfig and build process James Smart
2020-04-12 6:16 ` kbuild test robot
2020-04-12 6:16 ` kbuild test robot
2020-04-12 7:56 ` kbuild test robot
2020-04-12 7:56 ` kbuild test robot
2020-04-16 13:15 ` Daniel Wagner
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=202004121504.E6ItoFUo%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.