From: Rob Herring <robh@kernel.org>
To: kenchappa.demakkanavar@intel.com
Cc: furong.zhou@intel.com, dinguyen@kernel.org,
kris.pan@linux.intel.com, mgross@linux.intel.com,
will@kernel.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, kris.pan@intel.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
mark.gross@intel.com
Subject: Re: [PATCH v3 2/3] dt-bindings: arm: Add Thunder Bay bindings
Date: Tue, 21 Sep 2021 17:05:51 -0500 [thread overview]
Message-ID: <YUpXP3vdxHwaMIX9@robh.at.kernel.org> (raw)
In-Reply-To: <1631771898-18702-3-git-send-email-kenchappa.demakkanavar@intel.com>
On Thu, 16 Sep 2021 11:28:17 +0530, kenchappa.demakkanavar@intel.com wrote:
> From: "Kenchappa, Demakkanavar" <kenchappa.demakkanavar@intel.com>
>
> Document Intel Movidius SoC code-named Thunder Bay, along with the
> Thunder Bay Full and Prime configuration board.
>
> Add maintainers for the new Intel Movidius SoC code-named Thunder Bay.
>
> Signed-off-by: Kris, Pan <kris.pan@intel.com>
> Signed-off-by: Kenchappa, Demakkanavar <kenchappa.demakkanavar@intel.com>
> ---
> .../devicetree/bindings/arm/intel,thunderbay.yaml | 27 ++++++++++++++++++++++
> MAINTAINERS | 5 ++++
> 2 files changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/intel,thunderbay.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-09-21 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 5:58 [PATCH v3 0/3] Add initial Thunder Bay SoC / Board support kenchappa.demakkanavar
2021-09-16 5:58 ` [PATCH v3 1/3] arm64: Add config for Thunder Bay SoC kenchappa.demakkanavar
2021-09-16 5:58 ` [PATCH v3 2/3] dt-bindings: arm: Add Thunder Bay bindings kenchappa.demakkanavar
2021-09-21 22:05 ` Rob Herring [this message]
2021-09-16 5:58 ` [PATCH v3 3/3] arm64: dts: add initial device tree for Thunder Bay SoC kenchappa.demakkanavar
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=YUpXP3vdxHwaMIX9@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=furong.zhou@intel.com \
--cc=kenchappa.demakkanavar@intel.com \
--cc=kris.pan@intel.com \
--cc=kris.pan@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=mgross@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=will@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).