From: "David S. Miller" <davem@redhat.com>
To: hadi@cyberus.ca
Cc: kaber@trash.net, netdev@oss.sgi.com
Subject: Re: [PATCH]: fix queue limits in multiple qdiscs
Date: Tue, 18 Nov 2003 17:34:57 -0800 [thread overview]
Message-ID: <20031118173457.5c85c671.davem@redhat.com> (raw)
In-Reply-To: <1069081284.1024.23.camel@jzny.localdomain>
On 17 Nov 2003 10:01:24 -0500
jamal <hadi@cyberus.ca> wrote:
> Like i said it is valid - but i wouldnt go out of my way to fix it
> (especially when 2.6 is frozen).
I agree with this sentiment, but only in part.
Considering:
1) The output from 'tc' is very confusing and quite stupid.
2) Patrick did all the work to fix this bug.
3) His patch is %100 straight forward, simply, and easy to verify.
I am going to apply his patch.
Thanks Patrick.
prev parent reply other threads:[~2003-11-19 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 14:50 [PATCH]: fix queue limits in multiple qdiscs Patrick McHardy
2003-11-17 14:22 ` jamal
2003-11-17 14:47 ` Patrick McHardy
2003-11-17 15:01 ` jamal
2003-11-19 1:34 ` David S. Miller [this message]
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=20031118173457.5c85c671.davem@redhat.com \
--to=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).