From: kbuild test robot <lkp@intel.com>
To: Vignesh R <vigneshr@ti.com>
Cc: kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, Vignesh R <vigneshr@ti.com>
Subject: Re: [PATCH v3 1/2] spi: Add DMA support for spi_flash_read()
Date: Wed, 8 Jun 2016 06:29:38 +0800 [thread overview]
Message-ID: <201606080659.2i234CnZ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160607081810.6640-2-vigneshr@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]
Hi,
[auto build test ERROR on spi/for-next]
[also build test ERROR on v4.7-rc2 next-20160607]
[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/Vignesh-R/spi-Add-DMA-support-for-ti-qspi/20160607-162134
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi for-next
config: m32r-allyesconfig (attached as .config)
compiler: m32r-linux-gcc (GCC) 4.9.0
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=m32r
All errors (new ones prefixed by >>):
drivers/spi/spi.c: In function 'spi_flash_read':
>> drivers/spi/spi.c:2758:3: error: implicit declaration of function 'spi_map_buf' [-Werror=implicit-function-declaration]
ret = spi_map_buf(master, rx_dev, &msg->rx_sg,
^
>> drivers/spi/spi.c:2766:3: error: implicit declaration of function 'spi_unmap_buf' [-Werror=implicit-function-declaration]
spi_unmap_buf(master, rx_dev, &msg->rx_sg,
^
cc1: some warnings being treated as errors
vim +/spi_map_buf +2758 drivers/spi/spi.c
2752 }
2753 }
2754
2755 mutex_lock(&master->bus_lock_mutex);
2756 if (master->dma_rx) {
2757 rx_dev = master->dma_rx->device->dev;
> 2758 ret = spi_map_buf(master, rx_dev, &msg->rx_sg,
2759 msg->buf, msg->len,
2760 DMA_FROM_DEVICE);
2761 if (!ret)
2762 msg->cur_msg_mapped = true;
2763 }
2764 ret = master->spi_flash_read(spi, msg);
2765 if (msg->cur_msg_mapped)
> 2766 spi_unmap_buf(master, rx_dev, &msg->rx_sg,
2767 DMA_FROM_DEVICE);
2768 mutex_unlock(&master->bus_lock_mutex);
2769
---
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: 35831 bytes --]
next prev parent reply other threads:[~2016-06-07 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 8:18 [PATCH v3 0/2] spi: Add DMA support for ti-qspi Vignesh R
2016-06-07 8:18 ` [PATCH v3 1/2] spi: Add DMA support for spi_flash_read() Vignesh R
2016-06-07 22:29 ` kbuild test robot [this message]
2016-06-08 6:51 ` Vignesh R
2016-06-07 8:18 ` [PATCH v3 2/2] spi: spi-ti-qspi: Add DMA support for QSPI mmap read Vignesh R
2016-06-07 9:17 ` Peter Ujfalusi
2016-06-08 6:53 ` Vignesh R
2016-06-07 10:00 ` 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=201606080659.2i234CnZ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).