From: Rob Herring <robh@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: shawnguo@kernel.org, s.hauer@pengutronix.de, robh+dt@kernel.org,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
darshak.patel@einfochips.com, prajose.john@einfochips.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH 1/3] dt-bindings: arm: Add devicetree binding for Thor96 Board
Date: Tue, 29 Oct 2019 14:37:42 -0500 [thread overview]
Message-ID: <20191029193742.GA14965@bogus> (raw)
In-Reply-To: <20191024144235.3182-2-manivannan.sadhasivam@linaro.org>
On Thu, 24 Oct 2019 20:12:33 +0530, Manivannan Sadhasivam wrote:
> Add devicetree binding for Thor96 Board from Einfochips. This board is
> one of the 96Boards Consumer Edition platform powered by NXP i.MX8MQ SoC.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-10-29 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 14:42 [PATCH 0/3] Add support for Thor96 board Manivannan Sadhasivam
2019-10-24 14:42 ` [PATCH 1/3] dt-bindings: arm: Add devicetree binding for Thor96 Board Manivannan Sadhasivam
2019-10-25 6:26 ` Marco Felsch
2019-10-25 7:19 ` Manivannan Sadhasivam
2019-10-25 12:15 ` Marco Felsch
2019-10-29 19:37 ` Rob Herring [this message]
2019-10-24 14:42 ` [PATCH 2/3] arm64: dts: freescale: Add devicetree support for Thor96 board Manivannan Sadhasivam
2019-10-28 11:51 ` Shawn Guo
2019-10-28 14:27 ` Manivannan Sadhasivam
2019-10-28 14:32 ` Shawn Guo
2019-10-28 14:36 ` Manivannan Sadhasivam
2019-10-24 14:42 ` [PATCH 3/3] mtd: spi-nor: Add support for w25q256jw Manivannan Sadhasivam
2019-10-28 11:50 ` Vignesh Raghavendra
2019-10-28 14:33 ` Manivannan Sadhasivam
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=20191029193742.GA14965@bogus \
--to=robh@kernel.org \
--cc=darshak.patel@einfochips.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=prajose.john@einfochips.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).