[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070529.014610.23017882.davem@davemloft.net>
Date: Tue, 29 May 2007 01:46:10 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: rpjday@...dspring.com
Cc: jengelh@...ux01.gwdg.de, linux-kernel@...r.kernel.org
Subject: Re: stuff ready to be deleted?
From: "Robert P. J. Day" <rpjday@...dspring.com>
Date: Tue, 29 May 2007 04:20:24 -0400 (EDT)
> On Tue, 29 May 2007, Jan Engelhardt wrote:
>
> >
> > On May 28 2007 18:25, Robert P. J. Day wrote:
> > >On Mon, 28 May 2007, Jan Engelhardt wrote:
> >
> > >> >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
> > >
> > >so ... does "obsolete" really mean "obsolete"?
> >
> > Have you taken a look at the Makefile? See this oddity:
> >
> > obj-$(CONFIG_NET_ACT_POLICE) += act_police.o
> > obj-$(CONFIG_NET_CLS_POLICE) += act_police.o
> >
> > So is the Kconfig entry all that is obsolete?
>
> ah, i hadn't noticed that. how odd. now i don't know *what* to
> think.
Look at what tests that config option in the code, not just
what the makefiles do.
-
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/
Powered by blists - more mailing lists