[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VE1PR04MB6638DAA60BE5910113D5DE0E89F60@VE1PR04MB6638.eurprd04.prod.outlook.com>
Date: Mon, 8 Jul 2019 02:01:30 +0000
From: Robin Gong <yibin.gong@....com>
To: Vinod Koul <vkoul@...nel.org>
CC: Stephen Rothwell <sfr@...b.auug.org.au>,
Zhangfei Gao <zhangfei.gao@...aro.org>,
John Garry <john.garry@...wei.com>,
Arnd Bergmann <arnd@...db.de>, Rob Herring <robh@...nel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Angelo Dureghello <angelo@...am.it>
Subject: RE: linux-next: build failure after merge of the slave-dma tree
On 06-07-19, 22:43, Vinod Koul <vkoul@...nel.org> wrote:
> > That's caused by 'of_irq_count' NOT export to global symbol, and I'm
> > curious why it has been here for so long since Zhangfei found it in
> > 2015.
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatc
> >
> hwork.kernel.org%2Fpatch%2F7404681%2F&data=02%7C01%7Cyibin.gon
> g%40
> >
> nxp.com%7C6172242dfadd4f71c09a08d70220bf6f%7C686ea1d3bc2b4c6fa92
> cd99c5
> >
> c301635%7C0%7C0%7C636980211986259586&sdata=L8v%2B1o5zfgIAS
> go4qr3pu
> > cQ%2Byox1irANsvRv5ZNLlLM%3D&reserved=0
>
> Yes this does not seem to be applied, perhaps Rob can explain why. But this was
> not exported how did you test it?
I had no such issue because I built in fsl-edma instead of Stephen's config with building module.
Powered by blists - more mailing lists