From: Dave Hansen <dave.hansen@intel.com>
To: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Prabhjot Khurana" <prabhjot.khurana@intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Tony Luck" <tony.luck@intel.com>,
"Tony Nguyen" <anthony.l.nguyen@intel.com>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Gross <markgross@kernel.org>,
Mark Gross <mgross@linux.intel.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH] MAINTAINERS: Drop Mark Gross
Date: Tue, 26 May 2026 11:28:52 -0700 [thread overview]
Message-ID: <d49c8dd6-e262-4626-990a-9ad914594642@intel.com> (raw)
In-Reply-To: <20260526173806.3227828-2-ukleinek@kernel.org>
On 5/26/26 10:38, Uwe Kleine-König wrote:
> EDAC-E752X
> -M: Mark Gross <markgross@kernel.org>
> L: linux-edac@vger.kernel.org
> -S: Maintained
> +S: Orphan
> F: drivers/edac/e752x_edac.c
...
Mark left Intel a few months ago. It's not an email infrastructure problem.
I've been periodically sending mail to all of the Intel folks in
MAINTAINERS and sending patches just like this when emails are bouncing.
I figure that if folks pop back up with a working email, these kinds of
changes are easy enough to revert.
I appreciate you taking care of this before I got to it!
Acked-by: Dave Hansen <dave.hansen@linux.intel.com>
next prev parent reply other threads:[~2026-05-26 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 17:38 [PATCH] MAINTAINERS: Drop Mark Gross Uwe Kleine-König
2026-05-26 18:28 ` Dave Hansen [this message]
2026-05-26 18:41 ` Konstantin Ryabitsev
2026-05-26 19:32 ` [PATCH v2] MAINTAINERS: Update Mark Gross's email contact Uwe Kleine-König
2026-05-27 13:56 ` Konstantin Ryabitsev
2026-06-09 10:59 ` Uwe Kleine-König
2026-06-09 14:26 ` Andy Shevchenko
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=d49c8dd6-e262-4626-990a-9ad914594642@intel.com \
--to=dave.hansen@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=mgross@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=prabhjot.khurana@intel.com \
--cc=tony.luck@intel.com \
--cc=ukleinek@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