From: Adrian Bunk <bunk@stusta.de>
To: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: /net/sched/Kconfig broken
Date: Thu, 17 Nov 2005 00:16:50 +0100 [thread overview]
Message-ID: <20051116231650.GR5735@stusta.de> (raw)
In-Reply-To: <20051116201020.GA15113@fargo>
On Wed, Nov 16, 2005 at 09:10:20PM +0100, David Gómez wrote:
> Hi David,
>
> On Nov 16 at 11:51:41, David S. Miller wrote:
> > From: David Gómez <david@pleyades.net>
> > Date: Wed, 16 Nov 2005 20:44:14 +0100
> >
> > > It's impossible to enable the U32 classifier in QoS submenu, to use it
> > > with the "tc" application. In fact there are 23 :-/ options and suboptions
> > > that are missing from the configuration because it seems that the Kconfig
> > > file is broken.
> >
> > I can enable this just fine by using "make config", making
> > sure to enable CONFIG_NET_SCHED, then CONFIG_NET_CLS_BASIC,
> > and then the necessary classifiers (including U32) are offered
> > to be enabled.
>
> Sorry for not giving more details. I'm using make menuconfig
> in a 2.6.14 kernel After selecting CONFIG_NET_SCHED and CONFIG_NET_CLS_BASIC
> i don't see new options, the last option visible is NET_CLS_ROUTE4.
And if you select NET_CLS_ROUTE4, this should automatically select
NET_CLS_ROUTE.
Are you saying that after enabling NET_CLS_ROUTE4, the option
NET_CLS_ROUTE is not set in your .config?
> thanks,
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-11-16 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 19:44 /net/sched/Kconfig broken David Gómez
2005-11-16 19:51 ` David S. Miller
2005-11-16 20:10 ` David Gómez
2005-11-16 22:47 ` David Gómez
2005-11-16 23:16 ` Adrian Bunk [this message]
2005-11-17 13:57 ` David Gómez
2005-11-17 15:51 ` Roman Zippel
2005-11-17 19:49 ` David Gómez
2005-11-17 23:22 ` David S. Miller
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=20051116231650.GR5735@stusta.de \
--to=bunk@stusta.de \
--cc=davem@davemloft.net \
--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