From: Patrick McHardy <kaber@trash.net>
To: Joerg Pommnitz <pommnitz@yahoo.com>
Cc: Jarek Poplawski <jarkao2@o2.pl>, netdev@vger.kernel.org
Subject: Re: Does tc-prio really work as advertised?
Date: Tue, 27 Nov 2007 14:18:38 +0100 [thread overview]
Message-ID: <474C192E.9080608@trash.net> (raw)
In-Reply-To: <677950.98010.qm@web51406.mail.re2.yahoo.com>
Joerg Pommnitz wrote:
> Great :-(. I went over the ChangeLogs for later kernel versions, but
> couldn't find anything.
>
> I'll try to come up with a working .config for the most current kernel
> that works on my hardware and test again.
>
> Do you have a pointer to the fix so that I could try to patch a 2.6.20
> kernel?
git-log net/sched/sch_prio.c:
commit dbaaa07a60edf71670b484a65e14400ab40c84f7
Author: Lucas Nussbaum <lucas.nussbaum@imag.fr>
Date: Thu Aug 30 22:35:46 2007 -0700
[NET_SCHED] sch_prio.c: remove duplicate call of tc_classify()
and
commit bdba91ec70fb5ccbdeb1c7068319adc6ea9e1a7d
Author: Patrick McHardy <kaber@trash.net>
Date: Mon Jul 30 17:07:14 2007 -0700
[NET_SCHED]: Fix prio/ingress classification logic error
Feel free to send patches against the still maintained -stable versions.
next prev parent reply other threads:[~2007-11-27 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 13:07 Does tc-prio really work as advertised? Joerg Pommnitz
2007-11-27 13:18 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-27 13:00 AW: " Joerg Pommnitz
2007-11-27 14:12 ` Jarek Poplawski
2007-11-30 18:39 ` Michael Blizek
2007-11-27 10:54 AW: " Joerg Pommnitz
2007-11-27 11:58 ` Jarek Poplawski
2007-11-27 12:29 ` Patrick McHardy
2007-11-27 9:28 Joerg Pommnitz
2007-11-27 9:58 ` Jarek Poplawski
2007-11-23 14:47 Joerg Pommnitz
2007-11-26 22:25 ` Jarek Poplawski
2007-11-27 6:46 ` Jarek Poplawski
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=474C192E.9080608@trash.net \
--to=kaber@trash.net \
--cc=jarkao2@o2.pl \
--cc=netdev@vger.kernel.org \
--cc=pommnitz@yahoo.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 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.