devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Barker <paul.barker@sancloud.com>
To: "Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org
Cc: Paul Barker <paul.barker@sancloud.com>,
	Marc Murphy <marc.murphy@sancloud.com>
Subject: [PATCH 4/4] MAINTAINERS: Adopt SanCloud dts files as supported
Date: Thu, 17 Jun 2021 10:33:30 +0100	[thread overview]
Message-ID: <20210617093330.9179-5-paul.barker@sancloud.com> (raw)
In-Reply-To: <20210617093330.9179-1-paul.barker@sancloud.com>

Myself and Marc are happy to maintain these device tree files going
forward.

Signed-off-by: Paul Barker <paul.barker@sancloud.com>
Acked-by: Marc Murphy <marc.murphy@sancloud.com>
---
 MAINTAINERS | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index bc0ceef87b73..70ff908ac891 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16234,6 +16234,12 @@ F:	drivers/phy/samsung/phy-s5pv210-usb2.c
 F:	drivers/phy/samsung/phy-samsung-usb2.c
 F:	drivers/phy/samsung/phy-samsung-usb2.h
 
+SANCLOUD BEAGLEBONE ENHANCED DEVICE TREE
+M:	Paul Barker <paul.barker@sancloud.com>
+R:	Marc Murphy <marc.murphy@sancloud.com>
+S:	Supported
+F:	arch/arm/boot/dts/am335x-sancloud*
+
 SC1200 WDT DRIVER
 M:	Zwane Mwaikambo <zwanem@gmail.com>
 S:	Maintained
-- 
2.26.2


      parent reply	other threads:[~2021-06-17  9:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  9:33 [PATCH 0/4] Add support for the SanCloud BBE Lite Paul Barker
2021-06-17  9:33 ` [PATCH 1/4] ARM: dts: am335x-boneblack: Extract HDMI config Paul Barker
2021-06-17  9:33 ` [PATCH 2/4] ARM: dts: am335x-sancloud-bbe: Extract common code Paul Barker
2021-06-17  9:33 ` [PATCH 3/4] ARM: dts: am335x-sancloud-bbe-lite: New devicetree Paul Barker
2021-06-18 16:02   ` Robert Nelson
2021-06-29 13:10     ` Paul Barker
2021-07-20  8:41       ` Paul Barker
2021-06-17  9:33 ` Paul Barker [this message]

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=20210617093330.9179-5-paul.barker@sancloud.com \
    --to=paul.barker@sancloud.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=marc.murphy@sancloud.com \
    --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).