From: kbuild test robot <lkp@intel.com>
To: Jiada Wang <jiada_wang@mentor.com>
Cc: kbuild-all@01.org, broonie@kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org,
fixed-term.Oleksij.Rempel@de.bosch.com, jiada_wang@mentor.com
Subject: Re: [PATCH 2/2] spi: imx: dynamic burst length adjust for DMA mode
Date: Wed, 8 Feb 2017 18:59:14 +0800 [thread overview]
Message-ID: <201702081810.ArDQruSX%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170208062028.22313-3-jiada_wang@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Hi Jiada,
[auto build test ERROR on next-20170207]
url: https://github.com/0day-ci/linux/commits/Jiada-Wang/improve-imx-spi-performance/20170208-142524
config: arm-arm5 (attached as .config)
compiler: arm-linux-gnueabi-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=arm
All errors (new ones prefixed by >>):
>> ERROR: "arm926_dma_flush_range" [drivers/spi/spi-imx.ko] undefined!
---
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: 28175 bytes --]
prev parent reply other threads:[~2017-02-08 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 6:20 [PATCH linux-next v1 0/2] improve imx spi performance Jiada Wang
2017-02-08 6:20 ` [PATCH 1/2] spi: imx: dynamic burst length adjust for PIO mode Jiada Wang
2017-02-14 18:20 ` Mark Brown
2017-05-01 10:15 ` Jiada Wang
2017-02-08 6:20 ` [PATCH 2/2] spi: imx: dynamic burst length adjust for DMA mode Jiada Wang
2017-02-08 8:46 ` kbuild test robot
2017-02-08 10:59 ` kbuild test robot [this message]
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=201702081810.ArDQruSX%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=fixed-term.Oleksij.Rempel@de.bosch.com \
--cc=jiada_wang@mentor.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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).