@Stijn, @Hannu: Thank you for your explanation, I got it by now and I'm totally wrong in interpreting the mvebu-patch. Sorry for causing this flurry.
If we stick to the mvebu-patch, what I still do not understand, is why this patch refreshing is needed here. According to https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/diff/?id=v4.4.30&id2=v4.4&dt=2 the file arch/arm/boot/dts/Makefile has never been changed by the kernel. So there's a local patch which makes changes to this Makefile? What may be my problem here is, that I'm totally stuck to the kernel changelog, which leads to my question: is it the case, that the patches getting refreshed here are not directly related to the upstream kernel changes. If so, wouldn't it be clearer (for people like me :) ) if there were two seperate patches (i.e. one for kernel update+refreshes itself and one for the internal refreshes (or refreshes that have been missed in previous updates) )? Best regards, P. Wassi _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev