On Thu, 02 Jan 2020, Sam Ravnborg wrote: > Hi Lee. > > How do de handle the two mfd related patches? > > > I have few fixes for atmel-hlcdc driver in this series as well > > as two reverts. > > Revert "drm: atmel-hlcdc: enable sys_clk during initalization." is > > due to the fix in in patch 2/5. > > > > Thank you, > > Claudiu Beznea > > > > Changes in v3: > > - changes dev_err() message in patch 4/6 > > - collect Acked-by tags > > > > Changes in v2: > > - introduce patch 3/6 > > - use dev_err() inpatch 4/6 > > - introduce patch 5/6 instead of reverting commit f6f7ad323461 > > ("drm/atmel-hlcdc: allow selecting a higher pixel-clock than requested") > > > > Claudiu Beznea (5): > > drm: atmel-hlcdc: use double rate for pixel clock only if supported > > drm: atmel-hlcdc: enable clock before configuring timing engine > > > mfd: atmel-hlcdc: add struct device member to struct > > atmel_hlcdc_regmap > > mfd: atmel-hlcdc: return in case of error > > Would it be OK to apply the to drm-misc-next, or shal they go in via > your mfd tree?
How are they related to the other patches? Do they have build-time dependencies on any of the other patches, or vice versa? -- Lee Jones [李琼斯] Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel