devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: "jason-jh.lin" <jason-jh.lin@mediatek.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno 
	<angelogioacchino.delregno@collabora.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Hsin-Yi Wang <hsinyi@chromium.org>, Fei Shao <fshao@chromium.org>,
	Moudy Ho <moudy.ho@mediatek.com>,
	"roy-cw.yeh" <roy-cw.yeh@mediatek.com>,
	CK Hu <ck.hu@mediatek.com>, Fabien Parent <fparent@baylibre.com>,
	Nancy Lin <nancy.lin@mediatek.com>,
	singo.chang@mediatek.com, DTML <devicetree@vger.kernel.org>,
	"moderated list:ARM/STM32 ARCHITECTURE" 
	<linux-stm32@st-md-mailman.stormreply.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"moderated list:ARM/Mediatek SoC support" 
	<linux-mediatek@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Project_Global_Chrome_Upstream_Group 
	<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v2 0/4] Fix MediaTek display dt-bindings issues
Date: Thu, 24 Mar 2022 16:19:59 -0500	[thread overview]
Message-ID: <Yjzgf10zAhrkpYde@robh.at.kernel.org> (raw)
In-Reply-To: <CAAOTY__kzL8YuGo-oKct4c_bL-Ch5rW8wBpkhOXkK+a10gNXVg@mail.gmail.com>

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

      reply	other threads:[~2022-03-24 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220309134702.9942-1-jason-jh.lin@mediatek.com>
2022-03-23 14:09 ` [PATCH v2 0/4] Fix MediaTek display dt-bindings issues Rob Herring
2022-03-24 13:25   ` Chun-Kuang Hu
2022-03-24 21:19     ` Rob Herring [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yjzgf10zAhrkpYde@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=airlied@linux.ie \
    --cc=alexandre.torgue@foss.st.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=ck.hu@mediatek.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=enric.balletbo@collabora.com \
    --cc=fparent@baylibre.com \
    --cc=fshao@chromium.org \
    --cc=hsinyi@chromium.org \
    --cc=jason-jh.lin@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=matthias.bgg@gmail.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=moudy.ho@mediatek.com \
    --cc=nancy.lin@mediatek.com \
    --cc=p.zabel@pengutronix.de \
    --cc=roy-cw.yeh@mediatek.com \
    --cc=singo.chang@mediatek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).