From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: stuff ready to be deleted?
Date: Mon, 28 May 2007 18:41:01 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705281840110.17870@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0705281818370.17410@localhost.localdomain>
On Mon, 28 May 2007, Robert P. J. Day wrote:
> On Mon, 28 May 2007, Jan Engelhardt wrote:
>
> >
> > On May 28 2007 16:15, Robert P. J. Day wrote:
> > >removing dead content from the tree:
> > >
> > >http://fsdev.net/wiki/index.php?title=Kernel_Janitor%27s_Todo_List
> > >
> > >currently, the list contains the items:
> > >
> > > * 4 Traffic policing
> >
> > CONFIG_NET_SCHED? CONFIG_NET_ACT_POLICE? Neither seems
> > marked as deprecated/obsoleted in Kconfig.
>
> the "traffic policing" entry in that list refers specifically to the
> config option "CLS_NET_POLICE" in net/sched/Kconfig:
>
> config NET_CLS_POLICE
> bool "Traffic Policing (obsolete)"
> depends on NET_CLS_ACT!=y
> select NET_ESTIMATOR
> ---help---
> Say Y here if you want to do traffic policing, i.e. strict
> bandwidth limiting. This option is obsoleted by the traffic
> policer implemented as action, it stays here for compatibility
> reasons.
>
> so ... does "obsolete" really mean "obsolete"?
whoops, the URL i gave above is only for the main page, not for the
specific "stuff to be removed" list here:
http://fsdev.net/wiki/index.php?title=Stuff_to_be_removed
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-05-28 22:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 20:15 Robert P. J. Day
2007-05-28 20:24 ` Jesper Juhl
2007-05-28 21:14 ` John Anthony Kazos Jr.
2007-05-28 21:23 ` Jesper Juhl
2007-05-28 20:44 ` Oliver Pinter
2007-05-28 20:52 ` Robert P. J. Day
2007-05-28 23:49 ` Daniel Hazelton
2007-05-28 22:24 ` Bill Davidsen
2007-05-28 22:29 ` Jeff Garzik
2007-05-29 8:34 ` Alan Cox
2007-05-29 8:47 ` David Miller
2007-05-28 21:18 ` Jiri Slaby
2007-05-28 21:30 ` Jan Engelhardt
2007-05-28 22:25 ` Robert P. J. Day
2007-05-28 22:41 ` Robert P. J. Day [this message]
2007-05-29 6:09 ` Jan Engelhardt
2007-05-29 8:20 ` Robert P. J. Day
2007-05-29 8:46 ` David Miller
2007-05-29 7:56 ` Geert Uytterhoeven
2007-05-29 13:04 ` Finn Thain
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.0705281840110.17870@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=jengelh@linux01.gwdg.de \
--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®