linux-kernel - Re: "whitespace coding style cleanup" broke coding style

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Feb 2012 09:27:33 +0100
From:	Armin Schindler <armin@...ware.de>
To:	Joe Perches <joe@...ches.com>
CC:	Tilman Schmidt <tilman@...p.cc>, Armin Schindler <mac@...ware.de>,
	Karsten Keil <isdn@...ux-pingi.de>,
	Jiri Slaby <jslaby@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>,
	Hansjoerg Lipp <hjlipp@....de>,
	gigaset307x-common@...ts.sourceforge.net,
	Jiri Slaby <jirislaby@...il.com>,
	David Miller <davem@...emloft.net>
Subject: Re: "whitespace coding style cleanup" broke coding style

On 02/29/2012 12:28 AM, Joe Perches wrote:
> On Wed, 2012-02-29 at 00:08 +0100, Tilman Schmidt wrote:
>> Am 28.02.2012 23:05, schrieb Joe Perches:
>>> On Tue, 2012-02-28 at 18:58 +0100, Tilman Schmidt wrote:
>>>> Please remember to CC the maintainers of the affected code this time.
>>> Karsten Keil is the nominal maintainer for
>>> all of drivers/isdn.
>> Look again.
>
> What I wrote is correct.
>
> I am aware there are 2 other ISDN sections
> and maintainers listed in MAINTAINERS.
>
> 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.

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...

regards,
Armin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/