Re: [PATCH v2 0/4] Fix MediaTek display dt-bindings issues

Re: [PATCH v2 0/4] Fix MediaTek display dt-bindings issues

[Rob Herring]

On Wed, Mar 9, 2022 at 7:47 AM jason-jh.lin <jason-jh.lin@mediatek.com> wrote:
>
> The vdosys0 series carried a nice dt-bindings conversion of the old
> txt documentation for the entire mediatek-drm driver, but some of
> the issues in there weren't seen.
>
> This series is fixing all of the issues pointed out by a
> `dt_binding_check` run, followed by `dtbs_check`.
>
> Change in v2:
> - remove mediatek,ethdr.yaml file
> - change include header of mediatek,ovl-2l.yaml from mt8173 to mt8183
>
> AngeloGioacchino Del Regno (3):
>   dt-bindings: display: mediatek, mutex: Fix mediatek, gce-events type
>   dt-bindings: display: mediatek, ovl: Fix 'iommu' required property
>     typo
>   dt-bindings: display: mediatek: Fix examples on new bindings
>
> jason-jh.lin (1):
>   Revert "dt-bindings: display: mediatek: add ethdr definition for
>     mt8195"

Can this series get applied soon? linux-next is still broken.

If it hits Linus' tree, I will be applying them.

Rob

Re: [PATCH v2 0/4] Fix MediaTek display dt-bindings issues

[Chun-Kuang Hu]

Hi, Rob:

Rob Herring <robh@kernel.org> 於 2022年3月23日 週三 下午10:10寫道：
>
> On Wed, Mar 9, 2022 at 7:47 AM jason-jh.lin <jason-jh.lin@mediatek.com> wrote:
> >
> > The vdosys0 series carried a nice dt-bindings conversion of the old
> > txt documentation for the entire mediatek-drm driver, but some of
> > the issues in there weren't seen.
> >
> > This series is fixing all of the issues pointed out by a
> > `dt_binding_check` run, followed by `dtbs_check`.
> >
> > Change in v2:
> > - remove mediatek,ethdr.yaml file
> > - change include header of mediatek,ovl-2l.yaml from mt8173 to mt8183
> >
> > AngeloGioacchino Del Regno (3):
> >   dt-bindings: display: mediatek, mutex: Fix mediatek, gce-events type
> >   dt-bindings: display: mediatek, ovl: Fix 'iommu' required property
> >     typo
> >   dt-bindings: display: mediatek: Fix examples on new bindings
> >
> > jason-jh.lin (1):
> >   Revert "dt-bindings: display: mediatek: add ethdr definition for
> >     mt8195"
>
> Can this series get applied soon? linux-next is still broken.
>
> If it hits Linus' tree, I will be applying them.

I've applied this series to my tree [1], but now is merge window, so I
plan to send this series through Dave's tree after 5.18-rc1. Would
this be too late for you?

[1] https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux.git/log/?h=mediatek-drm-fixes

Regards,
Chun-Kuang.

>
> Rob

Re: [PATCH v2 0/4] Fix MediaTek display dt-bindings issues

[Rob Herring]

On Thu, Mar 24, 2022 at 09:25:44PM +0800, Chun-Kuang Hu wrote:
> Hi, Rob:
> 
> Rob Herring <robh@kernel.org> 於 2022年3月23日 週三 下午10:10寫道：
> >
> > On Wed, Mar 9, 2022 at 7:47 AM jason-jh.lin <jason-jh.lin@mediatek.com> wrote:
> > >
> > > The vdosys0 series carried a nice dt-bindings conversion of the old
> > > txt documentation for the entire mediatek-drm driver, but some of
> > > the issues in there weren't seen.
> > >
> > > This series is fixing all of the issues pointed out by a
> > > `dt_binding_check` run, followed by `dtbs_check`.
> > >
> > > Change in v2:
> > > - remove mediatek,ethdr.yaml file
> > > - change include header of mediatek,ovl-2l.yaml from mt8173 to mt8183
> > >
> > > AngeloGioacchino Del Regno (3):
> > >   dt-bindings: display: mediatek, mutex: Fix mediatek, gce-events type
> > >   dt-bindings: display: mediatek, ovl: Fix 'iommu' required property
> > >     typo
> > >   dt-bindings: display: mediatek: Fix examples on new bindings
> > >
> > > jason-jh.lin (1):
> > >   Revert "dt-bindings: display: mediatek: add ethdr definition for
> > >     mt8195"
> >
> > Can this series get applied soon? linux-next is still broken.
> >
> > If it hits Linus' tree, I will be applying them.
> 
> I've applied this series to my tree [1], but now is merge window, so I
> plan to send this series through Dave's tree after 5.18-rc1. Would
> this be too late for you?

Yes, people base their development on -rc1 and it would be nice to have 
a functional tree.

There's not really any need to wait to send fixes.

Rob