From: kbuild test robot <lkp@intel.com>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: kbuild-all@01.org, Eric Piel <eric.piel@tremplin-utc.net>,
linux-kernel@vger.kernel.org,
Marcus Folkesson <marcus.folkesson@gmail.com>
Subject: Re: [PATCH] mfd: mc13xxx-spi: make SPI buffers DMA-safe
Date: Tue, 20 Dec 2016 06:43:19 +0800 [thread overview]
Message-ID: <201612200628.H2XorK7M%fengguang.wu@intel.com> (raw)
In-Reply-To: <20161209102517.30745-1-marcus.folkesson@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
Hi Marcus,
[auto build test ERROR on ljones-mfd/for-mfd-next]
[also build test ERROR on v4.9 next-20161219]
[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/Marcus-Folkesson/mfd-mc13xxx-spi-make-SPI-buffers-DMA-safe/20161209-212034
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: s390-allmodconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
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=s390
All errors (new ones prefixed by >>):
drivers/mfd/mc13xxx-spi.c: In function 'mc13xxx_spi_read':
>> drivers/mfd/mc13xxx-spi.c:71:20: error: 'struct mc13xxx' has no member named 'wbuf'
.tx_buf = mc13xxx->wbuf,
^~
>> drivers/mfd/mc13xxx-spi.c:72:20: error: 'struct mc13xxx' has no member named 'rbuf'
.rx_buf = mc13xxx->rbuf,
^~
drivers/mfd/mc13xxx-spi.c:82:9: error: 'struct mc13xxx' has no member named 'wbuf'
mc13xxx->wbuf[0] = *(unsigned char *)reg;
^~
drivers/mfd/mc13xxx-spi.c:87:20: error: 'struct mc13xxx' has no member named 'rbuf'
memcpy(p, &mc13xxx->rbuf[1], 3);
^~
vim +71 drivers/mfd/mc13xxx-spi.c
65 {
66 unsigned char *p = val;
67 struct device *dev = context;
68 struct spi_device *spi = to_spi_device(dev);
69 struct mc13xxx *mc13xxx = dev_get_drvdata(dev);
70 struct spi_transfer t = {
> 71 .tx_buf = mc13xxx->wbuf,
> 72 .rx_buf = mc13xxx->rbuf,
73 .len = 4,
74 };
75
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 43192 bytes --]
next prev parent reply other threads:[~2016-12-19 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 10:25 Marcus Folkesson
2016-12-19 22:43 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-09 10:24 Marcus Folkesson
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=201612200628.H2XorK7M%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=eric.piel@tremplin-utc.net \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@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®