RE: linux-next: build failure after merge of the rpmsg tree

2019-02-22 Thread Loic PALLARDY
Loic PALLARDY > > Subject: Re: linux-next: build failure after merge of the rpmsg tree > > FYI, can I please get an explanation for the remoteproc changes? > > We really should avoid adding new callers of > dma_declare_coherent_memory, > which is a rather badly designed interface.

Re: linux-next: build failure after merge of the rpmsg tree

2019-02-22 Thread Christoph Hellwig
FYI, can I please get an explanation for the remoteproc changes? We really should avoid adding new callers of dma_declare_coherent_memory, which is a rather badly designed interface.

Re: linux-next: build failure after merge of the rpmsg tree

2018-04-25 Thread Bjorn Andersson
On Wed 25 Apr 20:33 PDT 2018, Stephen Rothwell wrote: > Hi Bjorn, > > After merging the rpmsg tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/remoteproc/remoteproc_core.c: In function 'rproc_handle_devmem': > drivers/remoteproc/remoteproc_core.c:557:8: err

Re: linux-next: build failure after merge of the rpmsg tree

2017-08-31 Thread Bjorn Andersson
On Wed 30 Aug 23:54 PDT 2017, Stephen Rothwell wrote: > Hi Bjorn, > > After merging the rpmsg tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > ERROR: "qcom_glink_native_probe" [drivers/rpmsg/qcom_glink_rpm.ko] undefined! > ERROR: "qcom_glink_native_remove" [drivers/rp