From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Mark Gross <markgross@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
linux-edac@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Tony Luck <tony.luck@intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v3] MAINTAINERS: Drop Mark Gross
Date: Fri, 3 Jul 2026 19:38:03 +0200 [thread overview]
Message-ID: <20260703173803.3589003-2-ukleinek@kernel.org> (raw)
Sending mail to Mark's Intel address results in the intel mail
server rejecting the mail. Dave Hansen confirmed he left Intel.
The kernel.org address seems to work, but there was no reply from Mark
on the discussion about broken email settings and his maintainer
entries.
So drop him from all maintainer entries.
Signed-off-by: Uwe Kleine-König <ukleinek@kernel.org>
---
Hello,
this patch was already send end of May (v1 @
https://lore.kernel.org/all/20260526173806.3227828-2-ukleinek@kernel.org).
Konstantin then suggested to change the maintainer contacts to the
kernel.org address as at least one of the forward-addresses for the
kernel.org account didn't bounce. This v2
(https://lore.kernel.org/all/20260526193238.3622176-2-ukleinek@kernel.org)
wasn't picked up yet, but given the continued silence I think removing
Mark completely is the saner choice now.
If someone has a better contact, please make him react. If he returns
later, the entries can easily get restored.
Best regards
Uwe
MAINTAINERS | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index f96621b3214c..d5260c8e9af5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9354,9 +9354,8 @@ S: Supported
F: drivers/edac/dmc520_edac.c
EDAC-E752X
-M: Mark Gross <markgross@kernel.org>
L: linux-edac@vger.kernel.org
-S: Maintained
+S: Orphan
F: drivers/edac/e752x_edac.c
EDAC-E7XXX
@@ -13211,7 +13210,6 @@ F: drivers/crypto/intel/keembay/ocs-aes.h
INTEL KEEM BAY OCS ECC CRYPTO DRIVER
M: Prabhjot Khurana <prabhjot.khurana@intel.com>
-M: Mark Gross <mgross@linux.intel.com>
S: Maintained
F: Documentation/devicetree/bindings/crypto/intel,keembay-ocs-ecc.yaml
F: drivers/crypto/intel/keembay/Kconfig
@@ -26683,8 +26681,7 @@ S: Maintained
F: drivers/net/ethernet/tehuti/tn40*
TELECOM CLOCK DRIVER FOR MCPL0010
-M: Mark Gross <markgross@kernel.org>
-S: Supported
+S: Orphan
F: drivers/char/tlclk.c
TEMPO SEMICONDUCTOR DRIVERS
base-commit: 2b763db0c2763d6bf73d7d3e69665222d1f377cf
--
2.55.0.11.g153666a7d9bb
next reply other threads:[~2026-07-03 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 17:38 Uwe Kleine-König [this message]
2026-07-03 17:43 ` [PATCH v3] MAINTAINERS: Drop Mark Gross Borislav Petkov
2026-07-04 0:40 ` Andrew Morton
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=20260703173803.3589003-2-ukleinek@kernel.org \
--to=ukleinek@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=konstantin@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=tony.luck@intel.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