public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Gómez" <david@pleyades.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: /net/sched/Kconfig broken
Date: Thu, 17 Nov 2005 14:57:31 +0100	[thread overview]
Message-ID: <20051117135731.GA11238@fargo> (raw)
In-Reply-To: <20051116231650.GR5735@stusta.de>

Hi Adrian,

On Nov 17 at 12:16:50, Adrian Bunk wrote:
> > 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?

No, the option is set. But the changes are not visible in make menuconfig, that
is, i cannot select options that depend on NET_CLS_ROUTE.

I found out that if i select NET_CLS_ROUTE4, save my changes and exit
menuconfig, execute again make menuconfig and go to QoS options, then the new
available options are visible. So menuconfig has some problem refreshing
contents :?

thanks,

-- 
David Gómez                                      Jabber ID: davidge@jabber.org

  reply	other threads:[~2005-11-17 13:57 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
2005-11-17 13:57       ` David Gómez [this message]
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=20051117135731.GA11238@fargo \
    --to=david@pleyades.net \
    --cc=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