From: kbuild test robot <lkp@intel.com>
To: Anshul Garg <aksgarg1989@gmail.com>
Cc: kbuild-all@01.org, jic23@kernel.org, knaack.h@gmx.de,
lars@metafoo.de, pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, Anshul Garg <aksgarg1989@gmail.com>
Subject: Re: [PATCH] iio/inkern.c Use list_for_each_entry_safe
Date: Wed, 9 Dec 2015 01:14:59 +0800 [thread overview]
Message-ID: <201512090100.JUJGFMt6%fengguang.wu@intel.com> (raw)
In-Reply-To: <1449592976-34591-1-git-send-email-aksgarg1989@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2287 bytes --]
Hi Anshul,
[auto build test ERROR on v4.4-rc4]
[also build test ERROR on next-20151208]
url: https://github.com/0day-ci/linux/commits/Anshul-Garg/iio-inkern-c-Use-list_for_each_entry_safe/20151209-005155
config: sh-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=sh
All errors (new ones prefixed by >>):
drivers/iio/inkern.c: In function 'iio_map_array_unregister':
>> drivers/iio/inkern.c:67:2: error: 'struct iio_map_internal' has no member named 'list'
drivers/iio/inkern.c:67:2: error: 'iio_map_listi' undeclared (first use in this function)
drivers/iio/inkern.c:67:2: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/iio/inkern.c:67:2: error: 'struct iio_map_internal' has no member named 'list'
>> drivers/iio/inkern.c:67:2: error: 'struct iio_map_internal' has no member named 'list'
>> drivers/iio/inkern.c:67:2: error: 'struct iio_map_internal' has no member named 'list'
>> drivers/iio/inkern.c:67:2: error: 'struct iio_map_internal' has no member named 'list'
drivers/iio/inkern.c:67:2: warning: left-hand operand of comma expression has no effect [-Wunused-value]
>> drivers/iio/inkern.c:67:2: error: 'struct iio_map_internal' has no member named 'list'
>> drivers/iio/inkern.c:67:2: error: 'struct iio_map_internal' has no member named 'list'
>> drivers/iio/inkern.c:67:2: error: 'struct iio_map_internal' has no member named 'list'
>> drivers/iio/inkern.c:67:2: error: 'struct iio_map_internal' has no member named 'list'
vim +67 drivers/iio/inkern.c
61 int iio_map_array_unregister(struct iio_dev *indio_dev)
62 {
63 int ret = -ENODEV;
64 struct iio_map_internal *mapi, *next;
65
66 mutex_lock(&iio_map_list_lock);
> 67 list_for_each_entry_safe(mapi, next, &iio_map_listi, list) {
68 if (indio_dev == mapi->indio_dev) {
69 list_del(&mapi->l);
70 kfree(mapi);
---
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: 37980 bytes --]
next prev parent reply other threads:[~2015-12-08 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 16:42 Anshul Garg
2015-12-08 17:02 ` kbuild test robot
2015-12-08 17:14 ` kbuild test robot [this message]
2015-12-08 17:45 Anshul Garg
2015-12-12 17:23 ` Jonathan Cameron
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=201512090100.JUJGFMt6%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aksgarg1989@gmail.com \
--cc=jic23@kernel.org \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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
all inboxes | Powered by JetHome®