From: Tony Lindgren <tony@atomide.com>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, afd@ti.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v7 0/2] dt-bindings: omap: Convert omap.txt to yaml
Date: Mon, 31 Jul 2023 09:08:19 +0300 [thread overview]
Message-ID: <20230731060819.GD5194@atomide.com> (raw)
In-Reply-To: <20230616185320.61b33510@aktux>
* Andreas Kemnade <andreas@kemnade.info> [230616 16:53]:
> On Tue, 13 Jun 2023 20:43:55 +0200
> Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
>
> > On 13/06/2023 19:32, Andreas Kemnade wrote:
> > > Hi,
> > >
> > > any action still expected from my side?
> > > people gave R-bys...
> > > So looks like it is ready for the dt-folks to pick it up.
> > >
> >
> > It's SoC file, isn't it? Then goes via SoC tree.
> >
> Apparently there was confusion about it. Quoting
> Tony:"And thanks for getting the
> omap.yaml conversion going, that will get merged by the dt folks."
>
> I am fine with either,
OK I'll apply this into omap-for-v6.6/dt-bindings thanks.
Regards,
Tony
prev parent reply other threads:[~2023-07-31 6:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 7:45 [PATCH v7 0/2] dt-bindings: omap: Convert omap.txt to yaml Andreas Kemnade
2023-05-15 7:45 ` [PATCH v7 1/2] dt-bindings: omap: Partially convert " Andreas Kemnade
2023-05-15 15:56 ` Krzysztof Kozlowski
2023-05-17 6:40 ` Tony Lindgren
2023-05-17 8:10 ` Andreas Kemnade
2023-05-17 10:09 ` Tony Lindgren
2023-05-15 7:45 ` [PATCH v7 2/2] MAINTAINERS: add board bindings list to OMAP2+ files Andreas Kemnade
2023-05-17 6:41 ` Tony Lindgren
2023-07-31 6:12 ` Tony Lindgren
2023-06-13 17:32 ` [PATCH v7 0/2] dt-bindings: omap: Convert omap.txt to yaml Andreas Kemnade
2023-06-13 18:43 ` Krzysztof Kozlowski
2023-06-16 16:53 ` Andreas Kemnade
2023-07-31 6:08 ` 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=20230731060819.GD5194@atomide.com \
--to=tony@atomide.com \
--cc=afd@ti.com \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@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).