From: kbuild test robot <lkp@intel.com>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: kbuild-all@01.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
gnurou@gmail.com, chunkeey@googlemail.com,
"Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: Re: [PATCH 1/2] gpio: mmio: add brcm,bcm6345 support
Date: Wed, 3 Aug 2016 19:28:13 +0800 [thread overview]
Message-ID: <201608031909.tunoWO7J%fengguang.wu@intel.com> (raw)
In-Reply-To: <1470222135-4731-1-git-send-email-noltari@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]
Hi Christian,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on next-20160803]
[cannot apply to v4.7]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/lvaro-Fern-ndez-Rojas/gpio-mmio-add-brcm-bcm6345-support/20160803-191501
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
config: sparc64-allyesconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 5.4.0-6) 5.4.0 20160609
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=sparc64
All errors (new ones prefixed by >>):
drivers/gpio/gpio-mmio.c: In function 'bgpio_parse_dt':
>> drivers/gpio/gpio-mmio.c:597:30: error: 'dev' undeclared (first use in this function)
if (of_device_is_big_endian(dev->of_node))
^
drivers/gpio/gpio-mmio.c:597:30: note: each undeclared identifier is reported only once for each function it appears in
vim +/dev +597 drivers/gpio/gpio-mmio.c
591 GFP_KERNEL);
592 if (!pdata)
593 return ERR_PTR(-ENOMEM);
594
595 pdata->base = -1;
596
> 597 if (of_device_is_big_endian(dev->of_node))
598 *flags |= BGPIOF_BIG_ENDIAN_BYTE_ORDER;
599
600 if (of_property_read_bool(pdev->dev.of_node, "no-output"))
---
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: 46987 bytes --]
next prev parent reply other threads:[~2016-08-03 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 11:02 Álvaro Fernández Rojas
2016-08-03 11:28 ` kbuild test robot [this message]
2016-08-03 11:38 ` kbuild test robot
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=201608031909.tunoWO7J%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chunkeey@googlemail.com \
--cc=gnurou@gmail.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noltari@gmail.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
all inboxes | Powered by JetHome®