From: Joe Perches <joe@perches.com>
To: Armin Schindler <armin@melware.de>
Cc: Tilman Schmidt <tilman@imap.cc>, Armin Schindler <mac@melware.de>,
Karsten Keil <isdn@linux-pingi.de>, Jiri Slaby <jslaby@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
Hansjoerg Lipp <hjlipp@web.de>,
gigaset307x-common@lists.sourceforge.net,
Jiri Slaby <jirislaby@gmail.com>,
David Miller <davem@davemloft.net>
Subject: Re: "whitespace coding style cleanup" broke coding style
Date: Wed, 29 Feb 2012 11:32:31 -0800 [thread overview]
Message-ID: <1330543951.21491.15.camel@joe2Laptop> (raw)
In-Reply-To: <4F4DE175.30002@melware.de>
On Wed, 2012-02-29 at 09:27 +0100, Armin Schindler wrote:
> On 02/29/2012 12:28 AM, Joe Perches wrote:
> > One of those, Armin Schindler, (cc'd) hasn't
> > signed a single commit in git history.
> True, my last work here was a long time ago.
> I used to maintain the eicon driver, but this driver
> is not just old, it is simply outdated for years and
> I doubt someone will ever use it in newer kernels.
> It just creates work here.
You could remove yourself from MAINTAINERS if you want.
MAINTAINERS | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5d3ae86..d40a974 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3682,10 +3682,9 @@ F: include/linux/isdn.h
F: include/linux/isdn/
ISDN SUBSYSTEM (Eicon active card driver)
-M: Armin Schindler <mac@melware.de>
L: isdn4linux@listserv.isdn4linux.de (subscribers-only)
W: http://www.melware.de
-S: Maintained
+S: Orphan
F: drivers/isdn/hardware/eicon/
IT87 HARDWARE MONITORING DRIVER
> Some time ago I asked (I don't remember who) why
> don't we remove that old driver from the kernel.
> It wasn't done because there is no follow up for the
> kernel. The new drivers out there are maintained,
> but will never be part of the kernel (coding style, etc.).
> I guess the idea was not to remove a driver from the kernel
> when there is no alternative (in kernel).
> Maybe I should bring this up again and ask for a removal of the
> current eicon driver in kernel...
Your choice.
It could be moved to staging as a prelude to removing
it after a few releases.
I did do a rather large drive-by whitespace cleanup
of eicon. It still compiles. I've no idea if it
still works though.
cheers, Joe
next prev parent reply other threads:[~2012-02-29 19:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 8:59 Jiri Slaby
2012-02-27 11:19 ` Tilman Schmidt
2012-02-27 11:34 ` Jiri Slaby
2012-02-27 16:52 ` Joe Perches
2012-02-27 17:12 ` Jiri Slaby
2012-02-27 17:27 ` Joe Perches
2012-02-27 17:39 ` [PATCH net-next] gigaset: Use semicolons to terminate statements Joe Perches
2012-02-27 19:12 ` David Miller
2012-02-27 18:58 ` "whitespace coding style cleanup" broke coding style Jiri Slaby
2012-02-28 17:58 ` Tilman Schmidt
2012-02-28 22:05 ` Joe Perches
2012-02-28 23:08 ` Tilman Schmidt
2012-02-28 23:28 ` Joe Perches
2012-02-28 23:42 ` David Miller
2012-02-29 0:41 ` Alan Cox
2012-02-29 8:27 ` Armin Schindler
2012-02-29 19:32 ` Joe Perches [this message]
2012-02-29 11:05 ` Tilman Schmidt
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=1330543951.21491.15.camel@joe2Laptop \
--to=joe@perches.com \
--cc=armin@melware.de \
--cc=davem@davemloft.net \
--cc=gigaset307x-common@lists.sourceforge.net \
--cc=hjlipp@web.de \
--cc=isdn@linux-pingi.de \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mac@melware.de \
--cc=tilman@imap.cc \
/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®