From: kbuild test robot <fengguang.wu@intel.com>
To: Alexandre TORGUE <alexandre.torgue@st.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Gerald Baeza <gerald.baeza@st.com>
Subject: ERROR: "bad_dma_ops" [drivers/tty/serial/stm32-usart.ko] undefined!
Date: Sun, 16 Oct 2016 18:08:08 +0800 [thread overview]
Message-ID: <201610161800.6qHF6rmq%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
Hi Alexandre,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 1001354ca34179f3db924eb66672442a173147dc
commit: 3489187204eb75e5635d8836babfd0a18be613f4 serial: stm32: adding dma support
date: 3 weeks ago
config: m32r-allmodconfig (attached as .config)
compiler: m32r-linux-gcc (GCC) 6.2.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
git checkout 3489187204eb75e5635d8836babfd0a18be613f4
# save the attached .config to linux build tree
make.cross ARCH=m32r
All errors (new ones prefixed by >>):
ERROR: "bad_dma_ops" [sound/soc/bcm/snd-soc-cygnus.ko] undefined!
ERROR: "bad_dma_ops" [sound/core/snd-pcm.ko] undefined!
ERROR: "dma_common_mmap" [sound/core/snd-pcm.ko] undefined!
>> ERROR: "bad_dma_ops" [drivers/tty/serial/stm32-usart.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: 36245 bytes --]
next reply other threads:[~2016-10-16 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 10:08 kbuild test robot [this message]
2016-10-23 9:54 kbuild test robot
2016-10-24 7:44 ` Alexandre Torgue
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=201610161800.6qHF6rmq%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=alexandre.torgue@st.com \
--cc=gerald.baeza@st.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®