All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Maietta <dave@qix.net>
To: linux-kernel@vger.kernel.org
Cc: trivial@rustcorp.com.au
Subject: [TRIVIAL][PATCH 2.4] Help dummies configure QoS
Date: 04 May 2003 19:53:18 -0400	[thread overview]
Message-ID: <1052092397.5844.33.camel@hell> (raw)

In the packet schedulers section of the config scripts, neither the
Ingress Qdisc nor any comment about its existence are displayed in
Menuconfig if some dependencies are not met in other places.  To help
dummies like me know that it's there, please consider the following
patch:

--- linux/net/sched/Config.in.orig	2003-05-04 18:50:54.000000000 -0400
+++ linux/net/sched/Config.in	2003-05-04 18:43:32.000000000 -0400
@@ -16,9 +16,6 @@
 tristate '  TBF queue' CONFIG_NET_SCH_TBF
 tristate '  GRED queue' CONFIG_NET_SCH_GRED
 tristate '  Diffserv field marker' CONFIG_NET_SCH_DSMARK
-if [ "$CONFIG_NETFILTER" = "y" ]; then
-   tristate '  Ingress Qdisc' CONFIG_NET_SCH_INGRESS
-fi
 bool '  QoS support' CONFIG_NET_QOS
 if [ "$CONFIG_NET_QOS" = "y" ]; then
    bool '    Rate estimator' CONFIG_NET_ESTIMATOR
@@ -38,4 +35,12 @@
       bool '    Traffic policing (needed for in/egress)'
CONFIG_NET_CLS_POLICE
    fi
 fi
+if [ "$CONFIG_NETFILTER" = "n" -o "$CONFIG_NET_QOS" = "n" -o \
+   "$CONFIG_NET_CLS" = "n" -o "$CONFIG_NET_CLS_POLICE" = "n" ]; then
+   comment '  Ingress Qdisc:  To enable, please include'
+   comment '    Network Packet Filtering, QoS Support,'
+   comment '    and Packet Classifier API/Traffic Policing'
+else
+   tristate '  Ingress Qdisc' CONFIG_NET_SCH_INGRESS
+fi
 


Thanks,
Dave Maietta
dave$qix,net


             reply	other threads:[~2003-05-04 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 23:53 Dave Maietta [this message]
2003-05-05  4:45 ` [TRIVIAL][PATCH 2.4] Help dummies configure QoS Rusty Russell

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=1052092397.5844.33.camel@hell \
    --to=dave@qix.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@rustcorp.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.