From: Colin Foster <colin.foster@in-advantage.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
soc@kernel.org, "Olof Johansson" <olof@lixom.net>,
"Arnd Bergmann" <arnd@arndb.de>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board
Date: Sun, 27 Nov 2022 15:13:35 -0800 [thread overview]
Message-ID: <Y4PvH1dW3FqHGRN8@euler> (raw)
In-Reply-To: <0a3b491c-7b91-4732-e280-3e49d9da01c6@linaro.org>
On Thu, Nov 24, 2022 at 12:53:32PM +0100, Krzysztof Kozlowski wrote:
> On 24/11/2022 00:32, Colin Foster wrote:
> > Add documentation for additional OMAP SOMs and development platforms,
> > provided by Phytec as the PCM-049 SOM and the PCM-959 development kit.
> >
> > Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
> > ---
> >
> > v1->v2
>
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Would be nice to convert the file to DT Schema.
Agreed. Thanks for the Ack despite this.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2022-11-27 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 23:32 [PATCH v2 0/2] add support for Phytec PCM-049 and PCM-959 Colin Foster
2022-11-23 23:32 ` [PATCH v2 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board Colin Foster
2022-11-24 11:53 ` Krzysztof Kozlowski
2022-11-27 23:13 ` Colin Foster [this message]
2022-11-23 23:32 ` [PATCH v2 2/2] arm: dts: omap4: pcm959: add initial support for phytec pcm959 Colin Foster
2022-11-24 11:57 ` Krzysztof Kozlowski
2022-11-27 23:44 ` Colin Foster
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=Y4PvH1dW3FqHGRN8@euler \
--to=colin.foster@in-advantage.com \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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 \
--cc=tony@atomide.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).