Hi, 22. 1. 17. 오후 6:55에 Robert Foss 이(가) 쓴 글: > Hi Inki, > > On Fri, 14 Jan 2022 at 02:18, Inki Dae <inki.dae@xxxxxxxxxxx> wrote: >> >> Hi Robert, >> >> 22. 1. 12. 오후 7:05에 Robert Foss 이(가) 쓴 글: >>> Thank you again for catching this and submitting a revert. >>> >>> Reviewed-by: Robert Foss <robert.foss@xxxxxxxxxx >>> >>> Applied to drm-misc-next. >>> >> >> Trivial thing I think but just notice. With this applying - original patch set and revert one, merge conflict may happen on drm-next because drm-misc-next has this patch set exynos-drm-next tree doesn't include. >> Leaving this patch history in drm-misc-next is correct? > > Thanks for paying attention to this. > > If we end up seeing a conflict, the exynos patches can go in through drm-misc. > I mean is it correct to leave some patch set history - which is not reviewed and even not tested - exists in management tree? Anyway, it depends on maintainer of this tree. :) Thanks, Inki Dae
