From: Aaron Erhardt <aer@tuxedocomputers.com>
To: "Werner Sembach" <wse@tuxedocomputers.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Aaron Erhardt <aer@tuxedocomputers.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 6/6] MAINTAINERS: Add Aaron Erhardt as maintainer of TUXEDO DRIVERS
Date: Mon, 28 Sep 2026 10:36:31 +0200 [thread overview]
Message-ID: <20260928085448.9024-7-aer@tuxedocomputers.com> (raw)
In-Reply-To: <20260928085448.9024-1-aer@tuxedocomputers.com>
I'm actively working on this driver as part of my responsibilities now.
Signed-off-by: Aaron Erhardt <aer@tuxedocomputers.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 140eafcbbd78..7b43a6e66d5c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -27870,6 +27870,7 @@ F: tools/testing/selftests/turbostat/
TUXEDO DRIVERS
M: Werner Sembach <wse@tuxedocomputers.com>
+M: Aaron Erhardt <aer@tuxedocomputers.com>
L: platform-driver-x86@vger.kernel.org
S: Supported
F: drivers/platform/x86/tuxedo/
--
2.43.0
prev parent reply other threads:[~2026-09-28 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 8:36 [PATCH v4 0/6] platform/x86/tuxedo: Fixes for TUXEDO NB04 driver Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 1/6] platform/x86/tuxedo: Don't use device driver data Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 2/6] platform/x86/tuxedo: Set HID report ID on success Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 3/6] platform/x86/tuxedo: Use intensity according to HID spec Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 4/6] platform/x86/tuxedo: Fix keyboard LED map ordering Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 5/6] platform/x86/tuxedo: Update and extend documentation Aaron Erhardt
2026-09-28 8:36 ` Aaron Erhardt [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=20260928085448.9024-7-aer@tuxedocomputers.com \
--to=aer@tuxedocomputers.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=wse@tuxedocomputers.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
all inboxes | Powered by JetHome®