On 06/02/2016 05:20 PM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/30/2016 03:28 AM, Krzysztof Kozlowski wrote: >> On 05/24/2016 03:31 PM, Marek Szyprowski wrote: >>> Once MFC driver has been converted to generic reserved memory bindings, >>> there is no need for custom memory reservation code. >>> >>> Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> >>> --- >>> arch/arm/mach-exynos/Makefile | 2 - >>> arch/arm/mach-exynos/exynos.c | 19 -------- >>> arch/arm/mach-exynos/mfc.h | 16 ------- >>> arch/arm/mach-exynos/s5p-dev-mfc.c | 93 -------------------------------------- >>> 4 files changed, 130 deletions(-) >>> delete mode 100644 arch/arm/mach-exynos/mfc.h >>> delete mode 100644 arch/arm/mach-exynos/s5p-dev-mfc.c >> >> Thanks, applied. >> > > This patch can't be applied before patches 2/5 and 3/5, or the custom > memory regions reservation will break with the current s5p-mfc driver. Yes, I know. As I understood from talk with Marek, the driver is broken now so continuous work was not chosen. If it is not correct and full bisectability is required, then entire patchset requires special handling - I need a stable tag from media tree. Without this everything will be broken anyway. Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
