Re: [alsa-devel] [PATCH 3/4] sound: arm: Add build system for bcm2835-analog-audio driver.

Am 14.03.2017 um 09:58 schrieb Michael Zoran:

On Tue, 2017-03-14 at 15:15 +0800, kbuild test robot wrote:

quoted

Hi Michael,

[auto build test ERROR on sound/for-next]
[also build test ERROR on v4.11-rc2 next-20170310]
[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/Michael-Zoran/dt-bin
dings-Document-the-dmas-and-dma-names-properties-for-bcm2835-analog-
audio/20170314-091035
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.g
it for-next
config: arm64-allmodconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master
/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=arm64 

All errors (new ones prefixed by >>):

   /tmp/ccNU8kQ5.s: Assembler messages:

quoted

quoted

/tmp/ccNU8kQ5.s:1411: Error: unknown mnemonic `ldmia' -- `ldmia
x26,{r0,r1,r2,r3}'
/tmp/ccNU8kQ5.s:1412: Error: unknown mnemonic `stmia' -- `stmia
x19!,{r0,r1,r2,r3}'
/tmp/ccNU8kQ5.s:1618: Error: unknown mnemonic `ldmia' -- `ldmia
x19!,{r0,r1,r2,r3}'
/tmp/ccNU8kQ5.s:1619: Error: unknown mnemonic `stmia' -- `stmia
x26,{r0,r1,r2,r3}'

---
0-DAY kernel test infrastructure                Open Source
Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel
Corporation

I'm a bit confused here.  Why I'm I seeing assembly instruction build
errors when the mail points to a DT binding document change?

The email subject doesn't refer to a DT binding.

I assume it's your change to enable ARM64 for all SND_ARM drivers, which
aren't aware of that.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html