linux-kernel - Re: stuff ready to be deleted?

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: <alpine.DEB.0.99.0705281712190.10522@sigma.j-a-k-j.com>
Date:	Mon, 28 May 2007 17:14:36 -0400 (EDT)
From:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
To:	Jesper Juhl <jesper.juhl@...il.com>
cc:	"Robert P. J. Day" <rpjday@...dspring.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: stuff ready to be deleted?

> >   i'm trying to keep track of kernel janitor projects that involve
> > removing dead content from the tree:
> > 
> > http://fsdev.net/wiki/index.php?title=Kernel_Janitor%27s_Todo_List
> > 
> > currently, the list contains the items:
> > 
> >     * 1 Legacy power management
> >     * 2 PCMCIA IOCTL support
> >     * 3 Traffic shaper
> >     * 4 Traffic policing
> >     * 5 Userspace queueing via NETLINK
> >     * 6 ebt: ulog support
> >     * 7 MOXA SmartIO support
> >     * 8 Old I2O ioctls
> >     * 9 Stallion drivers
> >     * 10 SDL RISCom/8 support
> >     * 11 Macintosh M68K support
> >     * 12 Commodore A2232 serial support
> >     * 13 CONFIG_FORCED_INLINING
> >     * 14 kernel_thread()
> > 
> > which of the above are legitimate candidates for removal?  which are
> > already underway in someone's local tree?  anything else that can
> > be added?  etc, etc.
> > 
> 
> Take a look at Documentation/feature-removal-schedule.txt
> Some of that stuff is already listed there along with who is in charge
> of removing it and when.

Let's not get in that catfight again. That file has been demonstrated to 
be half too premature and half completely obsolete. He's asking for which 
things should he start generating and sending patches and expect them to 
not be ignored or angrily shot down. feature-removal-schedule.txt does not 
provide this information, again as has been demonstrated.

Of course, it would be great if it were accurate and -did- provide that 
information.
-
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/