linux-kernel - Re: undeprecate raw driver.

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]

Message-ID: <Pine.LNX.4.64.0705131612050.3954@localhost.localdomain>
Date:	Sun, 13 May 2007 16:24:09 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	Bernd Eckenfels <ecki@...a.inka.de>, linux-kernel@...r.kernel.org
Subject: Re: undeprecate raw driver.

On Sun, 13 May 2007, Stefan Richter wrote:

> Except that the term "obsolete" is already used differently in the
> context of Linux kernel features; see Documentation/ABI/README.

no, it isn't.  in fact, it's used in that file *exactly* the way i've
been defining it:

"obsolete/"

"This directory documents interfaces that are still remaining in the
kernel, but are marked to be removed at some later point in time.
The description of the interface will document the reason why it is
obsolete and when it can be expected to be removed. The file
Documentation/feature-removal-schedule.txt may describe some of these
interfaces, giving a schedule for when they will be removed."

  note the salient points of what is considered "obsolete":

* yes, it's still in the kernel
* it may already be scheduled to be removed
* it's documented why that interface is ***obsolete*** and is
scheduled for removal

  look carefully, stefan -- note what's missing from that explanation:
the word "deprecated" which, IMHO, means something quite different.

  at this point, i've explained several times already what i think is
the difference between these two terms, and why i think it's an
*important* difference and how those terms should be used to guarantee
clarity.

  you clearly disagree and there's absolutely nothing i can say at
this point that's going to get through to you and i'm as thoroughly
tired of trying to explain it to you as i'm sure everyone else is of
reading it.  so let's just accept that any further discussion on this
topic is a waste of time.  and we can leave things the way they are,
and things will continue to be mis-labelled and people will, on a
regular basis, continue to submit patches to remove things that claim
to be "obsolete" but which aren't, and this whole freakin' debate will
start all over again.

  happy now?

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
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/