Am 02.11.2016 um 19:04 schrieb Andreas Färber:
Hi Matthias,
Am 02.11.2016 um 18:13 schrieb Matthias Brugger:
On 11/01/2016 08:55 PM, Andreas Färber wrote:
Am 24.10.2016 um 12:48 schrieb Andreas Färber: If I locally disable CONFIG_QCOM_WCNSS_PIL then no cycles get detected and it doesn't crash, finishing fine. But again, that's only a solution for getting some kernel built, not for getting sensible information on the next cycle...
Would you mind to try the patch attached? I suppose this fixes the building problem. [...]
Thanks for looking into this. On master branch I already reverted the config option to quickly un-block us. I don't think it blocks any enablement.
Bjorn is looking into the cycle and said this on ##linux-msm:
<bamse> oh no... vinod merged peter's patch to change remoteproc to be user selectable hmm, no that's not it
<bamse> ohh, never mind, it is broken...by my design sorry about that i have exported functions in both directions...how silly <bamse> afaerber: thanks for the report, i'll clean it up
So the cycle is being taken care of, now that I've identified it.
https://patchwork.kernel.org/patch/9411771/ Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org