From: Tony Lindgren <tony@atomide.com>
To: Andrew Davis <afd@ti.com>, Rob Herring <robh+dt@kernel.org>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Nishanth Menon" <nm@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] AM57x EVM Device Tree Overlays
Date: Wed, 9 Nov 2022 10:31:25 +0200 [thread overview]
Message-ID: <Y2tlXVA6CH/aSzeK@atomide.com> (raw)
In-Reply-To: <20221101221110.17885-1-afd@ti.com>
Hi Andrew & Rob,
* Andrew Davis <afd@ti.com> [221102 00:01]:
> Hello all,
>
> These is an uncontroversial (hopefully) DT Overlay to support the
> TI AM57x EVM. More complex cases are staged and ready to follow but
> wanted to test the water with this one.
>
> 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.
>
> Series depends on https://www.spinics.net/lists/kernel/msg4548509.html
Looks like we now have commit 26c9134a370a ("Merge branch 'dt/dtbo-rename'
into dt/next") in Linux next.
Can these two patches now be applied if I merge in the commit above?
Regards,
Tony
next prev parent reply other threads:[~2022-11-09 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 22:11 [PATCH v2 0/2] AM57x EVM Device Tree Overlays Andrew Davis
2022-11-01 22:11 ` [PATCH v2 1/2] ARM: dts: ti: Add AM57xx GP EVM board support Andrew Davis
2022-11-01 22:11 ` [PATCH v2 2/2] ARM: dts: ti: Add AM57xx GP EVM Rev A3 " Andrew Davis
2022-11-09 8:31 ` Tony Lindgren [this message]
2022-11-09 18:40 ` [PATCH v2 0/2] AM57x EVM Device Tree Overlays Andrew Davis
2022-11-10 7:12 ` Tony Lindgren
2023-01-19 8:22 ` Tony Lindgren
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=Y2tlXVA6CH/aSzeK@atomide.com \
--to=tony@atomide.com \
--cc=afd@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).