From: Tony Lindgren <tony@atomide.com>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: arnd@arndb.de, olof@lixom.net, soc@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
bcousson@baylibre.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap4: add initial support for Epson Moverio BT-200
Date: Wed, 31 May 2023 08:25:18 +0300 [thread overview]
Message-ID: <20230531052518.GU14287@atomide.com> (raw)
In-Reply-To: <20230515191735.6d671ef1@aktux>
* Andreas Kemnade <andreas@kemnade.info> [230515 17:17]:
> Hi,
>
> On Mon, 27 Mar 2023 11:21:37 +0300
> Tony Lindgren <tony@atomide.com> wrote:
>
> > * Andreas Kemnade <andreas@kemnade.info> [230313 13:04]:
> > > yes, epson,embt2ws is unknown, is the txt->yaml conversion around the
> > > corner? I would then resubmit it includding an addition
> > > to that yaml. If not probably I resubmit the conversion patch with
> > > the compatible added. But that should not stop the rest of this patch from
> > > being reviewed.
> >
> > Yeah let's do the yaml conversion first as otherwise we'll be adding some
> > extra warnings for the dt folks.
> >
> > Your patch looks otherwise OK to me.
> >
> do you expect any action from me here? As Krzysztof has given his
> Reviewed-by on the conversion patch, I would expect that it gets in right
> after that omap.yaml conversion patch if nobody objects.
Applying this into omap-for-v6.5/dt thanks. And thanks for getting the
omap.yaml conversion going, that will get merged by the dt folks.
Regards,
Tony
prev parent reply other threads:[~2023-05-31 5:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 11:04 [PATCH] ARM: dts: omap4: add initial support for Epson Moverio BT-200 Andreas Kemnade
2023-03-27 8:21 ` Tony Lindgren
2023-03-27 10:57 ` Andreas Kemnade
2023-05-15 17:17 ` Andreas Kemnade
2023-05-31 5:25 ` Tony Lindgren [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=20230531052518.GU14287@atomide.com \
--to=tony@atomide.com \
--cc=andreas@kemnade.info \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
/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).