From: Alexandre Torgue <alexandre.torgue@st.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: kbuild test robot <fengguang.wu@intel.com>, <kbuild-all@01.org>,
<linux-kernel@vger.kernel.org>,
Gerald Baeza <gerald.baeza@st.com>
Subject: Re: ERROR: "bad_dma_ops" [drivers/tty/serial/stm32-usart.ko] undefined!
Date: Mon, 24 Oct 2016 09:44:43 +0200 [thread overview]
Message-ID: <0093da0a-e1a2-da72-9827-a9a7200ba500@st.com> (raw)
In-Reply-To: <201610231743.Eq20tBqY%fengguang.wu@intel.com>
Hi Greg,
On 10/23/2016 11:54 AM, kbuild test robot wrote:
> Hi Alexandre,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
> commit: 3489187204eb75e5635d8836babfd0a18be613f4 serial: stm32: adding dma support
> date: 4 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!
>
This issue will be fixed by patch:
"[PATCH] serial: SERIAL_STM32 should depend on HAS_DMA"
sent by Geert Uytterhoeven.
Regards
Alex
next prev parent reply other threads:[~2016-10-24 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 9:54 kbuild test robot
2016-10-24 7:44 ` Alexandre Torgue [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-16 10:08 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=0093da0a-e1a2-da72-9827-a9a7200ba500@st.com \
--to=alexandre.torgue@st.com \
--cc=fengguang.wu@intel.com \
--cc=geert@linux-m68k.org \
--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®