From: Paul Barker <paul@pbarker.dev>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Barker <paul@pbarker.dev>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
Marc Murphy <marc.murphy@sancloud.com>
Subject: [PATCH] MAINTAINERS: Update email & status for SanCloud BBE dts files
Date: Thu, 21 Nov 2024 08:57:42 +0000 [thread overview]
Message-ID: <20241121085742.3037946-1-paul@pbarker.dev> (raw)
I am no longer employed by SanCloud, but I will continue to look after
the BBE device tree files using my own email address.
Signed-off-by: Paul Barker <paul@pbarker.dev>
Acked-by: Marc Murphy <marc.murphy@sancloud.com>
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a27407950242..0b20b60a212c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20451,9 +20451,9 @@ 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>
+M: Paul Barker <paul@pbarker.dev>
R: Marc Murphy <marc.murphy@sancloud.com>
-S: Supported
+S: Maintained
F: arch/arm/boot/dts/ti/omap/am335x-sancloud*
SC1200 WDT DRIVER
--
2.39.5
reply other threads:[~2024-11-21 8:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241121085742.3037946-1-paul@pbarker.dev \
--to=paul@pbarker.dev \
--cc=linux-kernel@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