mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: so what *is* obsolete and removable?
Date: Mon, 16 Apr 2007 10:44:52 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704161030040.6837@localhost.localdomain> (raw)
In-Reply-To: <9a8748490704151450i251b8b1av8439bc275e982866@mail.gmail.com>

On Sun, 15 Apr 2007, Jesper Juhl wrote:

> On 15/04/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> >
> >   in a recent posting, ian anderson suggested that, before kernel
> > features are removed, they should spend a reasonable amount of
> > time in the feature removal file to give everyone fair warning.
> > if that's the case, then there are a *bunch* of things that should
> > perhaps be added to that file real soon now just to start the
> > clock ticking.
> >
> [snip]
> > ./sound/oss/Kconfig:    bool "Obsolete OSS drivers"
> > ./sound/oss/Kconfig:      This option enables support for obsolete OSS
> > drivers that
> >
> >   clearly, that was a fairly brainless search, but it still
> > reveals a pile of stuff that's "obsolete" (whatever that means in
> > the context in which it's used).  so what's really obsolete?
> >
> IIRC Adrian Bunk is handling the removal of obsolete OSS drivers and
> doing a nice job at it. Dunno about the rest of the stuff.

oh, i realize that a number of those examples from my earlier post
were already handled/being handled (i don't even look under OSS these
days when doing any cleanup).

my point was that, if ian's position is valid and stuff shouldn't be
removed without fair warning, then a lot of that stuff should get
entered into the feature removal file real soon now.

rday

p.s.  again, if you run the simple grep i mentioned before:

  $ grep -iw obsolete $(find . -name Kconfig\*)

you find some odd combinations, such as this from net/ipv4/Kconfig:

config ARPD
        bool "IP: ARP daemon support (EXPERIMENTAL)"
        depends on EXPERIMENTAL
        ---help---
        ...
        This code is experimental and also obsolete...

the thought of something being both experimental *and* obsolete is a
bit weird, is it not?

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

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

  reply	other threads:[~2007-04-16 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 20:55 Robert P. J. Day
2007-04-15 21:45 ` Jiri Slaby
2007-04-15 21:50 ` Jesper Juhl
2007-04-16 14:44   ` Robert P. J. Day [this message]
2007-04-16 14:58     ` Adrian Bunk
2007-04-16 22:39 ` Tilman Schmidt
2007-04-16 23:13   ` Randy Dunlap
2007-04-17 12:52     ` Tilman Schmidt
2007-04-17 13:40       ` Alan Cox
2007-04-17 15:03         ` Tilman Schmidt
2007-04-17 15:33           ` Alan Cox
2007-04-17 17:55             ` 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=Pine.LNX.4.64.0704161030040.6837@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=bunk@stusta.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®