From: Tony Lindgren <tony@atomide.com>
To: Andrew Davis <afd@ti.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Colin Foster" <colin.foster@in-advantage.com>,
"Olof Johansson" <olof@lixom.net>,
"Arnd Bergmann" <arnd@arndb.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/3] AM57x EVM Device Tree Overlays
Date: Mon, 27 Mar 2023 11:10:05 +0300 [thread overview]
Message-ID: <20230327081005.GD7501@atomide.com> (raw)
In-Reply-To: <20230307161715.15209-1-afd@ti.com>
* Andrew Davis <afd@ti.com> [230307 18:17]:
> Hello all,
>
> These are a set of uncontroversial (hopefully) DT Overlays to support the
> TI AM57x EVM and displays for AM57x IDKs. More complex cases are staged
> and ready to follow, but wanted to test the water with these first.
Applying these into omap-for-v6.4/dt-overlays thanks.
> For some reason dtbs_check does not get run on overlays, this
> will need further investigation to fix in kbuild. For now I ran
> it through manually but am not 100% sure it actually checked it,
> so double checks here very welcome.
Seems like that's a separate patch from this series.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-27 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 16:17 [PATCH v4 0/3] AM57x EVM Device Tree Overlays Andrew Davis
2023-03-07 16:17 ` [PATCH v4 1/3] ARM: dts: ti: Add AM57xx GP EVM board support Andrew Davis
2023-03-07 16:17 ` [PATCH v4 2/3] ARM: dts: ti: Add AM57xx GP EVM Rev A3 " Andrew Davis
2023-03-07 16:17 ` [PATCH v4 3/3] ARM: dts: am57xx-idk: Add IDK displays and touchscreens Andrew Davis
2023-03-27 8:10 ` 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=20230327081005.GD7501@atomide.com \
--to=tony@atomide.com \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=colin.foster@in-advantage.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 \
/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).