On Tue, Jun 25, 2019 at 2:26 AM Linus Walleij <[email protected]> wrote:
>
> On Tue, Jun 25, 2019 at 12:47 AM Rob Herring <[email protected]> wrote:
> > On Mon, Jun 24, 2019 at 4:13 PM Linus Walleij <[email protected]> 
> > wrote:
> > > On Mon, Jun 24, 2019 at 11:59 PM Rob Herring <[email protected]> wrote:
> > >
> > > > Convert the tpo,tpg110 panel binding to DT schema.
> > > >
> > > > Cc: Linus Walleij <[email protected]>
> > > > Cc: Thierry Reding <[email protected]>
> > > > Cc: Sam Ravnborg <[email protected]>
> > > > Cc: Maxime Ripard <[email protected]>
> > > > Cc: Laurent Pinchart <[email protected]>
> > > > Cc: [email protected]
> > > > Signed-off-by: Rob Herring <[email protected]>
> > >
> > > Awesome, fixed up the MAINATINERS entry and applied and
> > > pushed for DRM next with my Reviewed-by.
> >
> > You shouldn't have because this is dependent on patch 2 and
> > panel-common.yaml. So now 'make dt_binding_check' is broken.
>
> Ooops easily happens when I am only adressee on this patch and
> there is no mention of any dependencies.

It's a series. I would assume the default is 1 person applies a series
unless explicitly stated otherwise.

> Can I simply just merge the panel-common patch as well and we
> are all happy?

I have drm-misc commit rights too, so I'll apply the whole lot when it's ready.

> I can also pick up more panel binding patches, IMO the yaml
> conversions are especially uncontroversial and should have low
> threshold for merging.

Yes, but the threshold is at least 'make dt_binding_check' should not
break. But don't worry, there are 2 other breakages in linux-next
currently.

Rob

Reply via email to