From: "David S. Miller" <davem@redhat.com>
To: devik <devik@cdi.cz>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org, daniel.blueman@gmx.net
Subject: Re: HTB 2.6.0-test10 oops related patch
Date: Sat, 6 Dec 2003 23:10:47 -0800 [thread overview]
Message-ID: <20031206231047.01257548.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0312061512320.839-200000@devix>
On Sat, 6 Dec 2003 15:18:37 +0100 (CET)
devik <devik@cdi.cz> wrote:
> I discovered reason of the first Daniel's OOPS. It is change
> which was not forward-ported to 2.6.
> It is attached.
Thanks a lot for tracking this problem down Devik.
Patch applied, thanks again.
next prev parent reply other threads:[~2003-12-07 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 16:10 [2.6.0-test9] QoS HTB crash Daniel Blueman
2003-10-30 19:50 ` devik
2003-10-30 21:08 ` David S. Miller
2003-10-31 7:40 ` devik
2003-11-01 18:13 ` Daniel Blueman
2003-12-06 14:18 ` HTB 2.6.0-test10 oops related patch devik
2003-12-07 7:10 ` David S. Miller [this message]
2003-12-07 11:30 ` devik
2003-12-07 23:29 ` 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=20031206231047.01257548.davem@redhat.com \
--to=davem@redhat.com \
--cc=daniel.blueman@gmx.net \
--cc=devik@cdi.cz \
--cc=linux-net@vger.kernel.org \
--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).