From: kbuild test robot <lkp@intel.com>
To: Brent Taylor <motobud@gmail.com>
Cc: kbuild-all@01.org, kvalo@qca.qualcomm.com,
linux-wireless@vger.kernel.org, netdev@vger.kenrel.org,
linux-kernel@vger.kernel.org, ath6kl@lists.infradead.org,
Brent Taylor <motobud@gmail.com>
Subject: Re: [PATCH v2] ath6kl: Use vmalloc for loading firmware using api1 method and use kvfree
Date: Sun, 29 Nov 2015 13:27:44 +0800 [thread overview]
Message-ID: <201511291301.8Pb6u5lz%fengguang.wu@intel.com> (raw)
In-Reply-To: <1448774038-26984-1-git-send-email-motobud@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Hi Brent,
[auto build test ERROR on: net-next/master]
[also build test ERROR on: v4.4-rc2 next-20151127]
url: https://github.com/0day-ci/linux/commits/Brent-Taylor/ath6kl-Use-vmalloc-for-loading-firmware-using-api1-method-and-use-kvfree/20151129-132013
config: x86_64-randconfig-x012-201548 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/net/wireless/ath/ath6kl/init.c: In function 'ath6kl_get_fw':
>> drivers/net/wireless/ath/ath6kl/init.c:679:9: error: too few arguments to function 'kmalloc'
*fw = kmalloc(fw_entry->size);
^
In file included from include/linux/textsearch.h:8:0,
from include/linux/skbuff.h:30,
from include/linux/if_ether.h:23,
from include/linux/etherdevice.h:25,
from drivers/net/wireless/ath/ath6kl/core.h:21,
from drivers/net/wireless/ath/ath6kl/init.c:28:
include/linux/slab.h:428:30: note: declared here
static __always_inline void *kmalloc(size_t size, gfp_t flags)
^
vim +/kmalloc +679 drivers/net/wireless/ath/ath6kl/init.c
673 return ret;
674
675 *fw_len = fw_entry->size;
676 if (&ar->fw == fw)
677 *fw = vmalloc(fw_entry->size);
678 else
> 679 *fw = kmalloc(fw_entry->size);
680
681 if (*fw == NULL)
682 ret = -ENOMEM;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 23835 bytes --]
next prev parent reply other threads:[~2015-11-29 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 5:10 [PATCH] ath6kl: Use vmalloc for loading firmware using api1 method Brent Taylor
2015-11-28 18:58 ` Brent Taylor
2015-11-29 0:53 ` Andy Shevchenko
2015-11-29 2:56 ` Tetsuo Handa
2015-11-29 5:13 ` [PATCH v2] ath6kl: Use vmalloc for loading firmware using api1 method and use kvfree Brent Taylor
2015-11-29 5:27 ` kbuild test robot [this message]
2015-11-29 5:51 ` [PATCH v3] " Brent Taylor
2015-11-30 8:48 ` Kalle Valo
2015-11-30 8:48 ` [PATCH v2] " Kalle Valo
2015-11-30 9:05 ` Kalle Valo
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=201511291301.8Pb6u5lz%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ath6kl@lists.infradead.org \
--cc=kbuild-all@01.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=motobud@gmail.com \
--cc=netdev@vger.kenrel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).