From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Joe Perches <joe@perches.com>, Jason Baron <jbaron@akamai.com>,
LKML <linux-kernel@vger.kernel.org>,
Doug Thompson <dougthompson@xmission.com>,
Linux Edac Mailing List <linux-edac@vger.kernel.org>
Subject: Re: MAINTAINERS without commits in the last 3 years
Date: Thu, 1 Sep 2016 14:58:36 +0200 [thread overview]
Message-ID: <20160901125836.GH24791@nazgul.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F3A1B02A0@ORSMSX114.amr.corp.intel.com>
On Fri, Aug 26, 2016 at 08:17:50PM +0000, Luck, Tony wrote:
> Agreed. I don't have a box to test, so I can't take on this driver. But leaving
> it in tree for a while longer doesn't hurt (much ... it seems to get a tree-wide
> cleanup patch about once a year ... which doesn't sound like a crushing
> overhead).
Here it is:
---
From: Borislav Petkov <bp@suse.de>
Date: Thu, 1 Sep 2016 14:55:45 +0200
Subject: [PATCH] EDAC, I3000: Orphan driver
Apparently there's no hw left at Intel for testing patches and Jason is
not going to maintain it anymore.
Signed-off-by: Borislav Petkov <bp@suse.de>
---
CREDITS | 4 ++++
MAINTAINERS | 3 +--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/CREDITS b/CREDITS
index 2a3fbcd229e6..1d7c43f3361f 100644
--- a/CREDITS
+++ b/CREDITS
@@ -3654,6 +3654,10 @@ S: Obere Heerbergstrasse 17
S: 97078 Wuerzburg
S: Germany
+N: Jason Uhlenkott
+E: juhlenko@akamai.com
+D: I3000 EDAC driver
+
N: Greg Ungerer
E: gerg@snapgear.com
D: uClinux kernel hacker
diff --git a/MAINTAINERS b/MAINTAINERS
index 20bb1d00098c..13c6abeb451a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4454,9 +4454,8 @@ S: Maintained
F: drivers/edac/i82443bxgx_edac.c
EDAC-I3000
-M: Jason Uhlenkott <juhlenko@akamai.com>
L: linux-edac@vger.kernel.org
-S: Maintained
+S: Orphan
F: drivers/edac/i3000_edac.c
EDAC-I5000
--
2.8.4
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2016-09-01 13:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 23:33 Joe Perches
[not found] ` <CA+i2_Ddvg9a0S23ywJtXQbLuq3JLJF9poH=n_G1+9uWWVPZwOg@mail.gmail.com>
2016-08-25 0:24 ` Joe Perches
[not found] ` <CAHrUA37xh-6GLkTAM75w8v550rR8n2Ayycjy9FNofv3K+=QoVQ@mail.gmail.com>
2016-08-25 2:09 ` Joe Perches
2016-08-25 3:26 ` Alexander Graf
2016-08-25 7:01 ` Ali Akcaagac
2016-08-25 7:29 ` Steve Twiss
2016-08-25 10:12 ` Mauro Carvalho Chehab
2016-08-25 16:12 ` David Carroll
2016-08-25 20:46 ` Steven French
2016-08-25 20:58 ` Greg KH
2016-08-26 0:33 ` Joe Perches
2016-08-26 12:59 ` Shuah Khan
2016-08-26 16:56 ` Florian Fainelli
2016-08-26 17:09 ` Joe Perches
2016-08-26 19:34 ` Jason Baron
2016-08-26 19:50 ` Joe Perches
2016-08-26 20:05 ` Borislav Petkov
2016-08-26 20:17 ` Luck, Tony
2016-09-01 12:58 ` Borislav Petkov [this message]
2016-09-01 16:02 ` Joe Perches
2016-09-02 5:26 ` Borislav Petkov
[not found] ` <CACwGpODqLAjQxgw=EdtWCKhFywy9btv9Ka6XG8YXbzKEBFPzEg@mail.gmail.com>
2016-08-28 2:40 ` Joe Perches
2016-08-30 15:19 ` Anders Larsen
2016-08-30 15:35 ` Joe Perches
2016-08-25 10:00 Tigran Aivazian
2016-08-25 10:09 ` Joe Perches
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=20160901125836.GH24791@nazgul.tnic \
--to=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=jbaron@akamai.com \
--cc=joe@perches.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®