devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniele Alessandrelli <daniele.alessandrelli@linux.intel.com>
To: linux-arm-kernel@lists.infradead.org, SoC Team <soc@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Jassi Brar <jassisinghbrar@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: devicetree@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-kernel@vger.kernel.org, Dinh Nguyen <dinguyen@kernel.org>,
	Paul Murphy <paul.j.murphy@intel.com>,
	Will Deacon <will@kernel.org>,
	Daniele Alessandrelli <daniele.alessandrelli@intel.com>
Subject: [PATCH v2 3/5] MAINTAINERS: Add maintainers for Keem Bay SoC
Date: Wed,  8 Jul 2020 18:50:18 +0100	[thread overview]
Message-ID: <20200708175020.194436-4-daniele.alessandrelli@linux.intel.com> (raw)
In-Reply-To: <20200708175020.194436-1-daniele.alessandrelli@linux.intel.com>

From: Daniele Alessandrelli <daniele.alessandrelli@intel.com>

Add maintainers for the new Intel Movidius SoC code-named Keem Bay.

Reviewed-by: Dinh Nguyen <dinguyen@kernel.org>
Signed-off-by: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
---
 MAINTAINERS | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1d4aa7f942de..ceb833fa04dd 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1954,6 +1954,14 @@ F:	drivers/irqchip/irq-ixp4xx.c
 F:	include/linux/irqchip/irq-ixp4xx.h
 F:	include/linux/platform_data/timer-ixp4xx.h
 
+ARM/INTEL KEEMBAY ARCHITECTURE
+M:	Paul J. Murphy <paul.j.murphy@intel.com>
+M:	Daniele Alessandrelli <daniele.alessandrelli@intel.com>
+S:	Maintained
+F:	Documentation/devicetree/bindings/arm/keembay.yaml
+F:	include/dt-bindings/clock/keembay-clocks.h
+F:	include/dt-bindings/power/keembay-power.h
+
 ARM/INTEL RESEARCH IMOTE/STARGATE 2 MACHINE SUPPORT
 M:	Jonathan Cameron <jic23@cam.ac.uk>
 L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
-- 
2.26.2


  parent reply	other threads:[~2020-07-08 17:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 17:50 [PATCH v2 0/5] Add initial Keem Bay SoC / Board support Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 1/5] arm64: Add config for Keem Bay SoC Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 2/5] dt-bindings: arm: Add Keem Bay bindings Daniele Alessandrelli
2020-07-14  3:12   ` Rob Herring
2020-07-14 13:29     ` Daniele Alessandrelli
2020-07-08 17:50 ` Daniele Alessandrelli [this message]
2020-07-08 17:50 ` [PATCH v2 4/5] arm64: dts: keembay: Add device tree for Keem Bay SoC Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 5/5] arm64: dts: keembay: Add device tree for Keem Bay EVM board Daniele Alessandrelli
2020-07-14 12:40 ` [PATCH v2 0/5] Add initial Keem Bay SoC / Board support Arnd Bergmann
2020-07-14 13:33   ` Daniele Alessandrelli

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=20200708175020.194436-4-daniele.alessandrelli@linux.intel.com \
    --to=daniele.alessandrelli@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=daniele.alessandrelli@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=paul.j.murphy@intel.com \
    --cc=robh+dt@kernel.org \
    --cc=soc@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).