On 09/01/2020 02:53, CK Hu wrote:
> Hi, Matthias:
>
> On Wed, 2020-01-08 at 13:05 +0100, Matthias Brugger wrote:
>> On 08/01/2020 12:14, Matthias Brugger wrote:
>>> Hi CK,
>>>
>>> On 07/01/2020 03:56, CK Hu wrote:
Hi, Dave, Daniel, Matthias:
In mediatek-drm-next-5.6 [1], I've che
Hi, Matthias:
On Wed, 2020-01-08 at 13:05 +0100, Matthias Brugger wrote:
> On 08/01/2020 12:14, Matthias Brugger wrote:
> > Hi CK,
> >
> > On 07/01/2020 03:56, CK Hu wrote:
> >> Hi, Dave, Daniel, Matthias:
> >>
> >> In mediatek-drm-next-5.6 [1], I've cherry-pick 3 patches from
> >> v5.5-next/soc
On 08/01/2020 12:14, Matthias Brugger wrote:
> Hi CK,
>
> On 07/01/2020 03:56, CK Hu wrote:
>> Hi, Dave, Daniel, Matthias:
>>
>> In mediatek-drm-next-5.6 [1], I've cherry-pick 3 patches from
>> v5.5-next/soc [2] because some drm patches depend on these cmdq patches.
>> So these cmdq patches exist
Hi CK,
On 07/01/2020 03:56, CK Hu wrote:
> Hi, Dave, Daniel, Matthias:
>
> In mediatek-drm-next-5.6 [1], I've cherry-pick 3 patches from
> v5.5-next/soc [2] because some drm patches depend on these cmdq patches.
> So these cmdq patches exist in both tree now. I want to know how to
> process this
Hi, Dave, Daniel, Matthias:
In mediatek-drm-next-5.6 [1], I've cherry-pick 3 patches from
v5.5-next/soc [2] because some drm patches depend on these cmdq patches.
So these cmdq patches exist in both tree now. I want to know how to
process this case. I think we could choose one of below way:
1. Be
