From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: Maillist netdev <netdev@oss.sgi.com>
Subject: Re: [PATCH PKT_SCHED 0/17]: tc action cleanup + fixes
Date: Thu, 30 Dec 2004 17:10:19 +0100 [thread overview]
Message-ID: <41D4286B.1060106@trash.net> (raw)
In-Reply-To: <41D3F5EC.9050808@trash.net>
Patrick McHardy wrote:
> Thanks, I'll continue later today and send another batch
> tonight.
Thinking about it, I think its better to reorganize the
patches by subject. While doing this I'm going to add
back the useful printks in the init paths as DPRINTKs.
I'm going to post the entire reorganized batch next week
when I return home, working with bitkeeper on my crappy
notebook is just to painful :)
Regards
Patrick
next prev parent reply other threads:[~2004-12-30 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 3:39 [PATCH PKT_SCHED 0/17]: tc action cleanup + fixes Patrick McHardy
2004-12-30 4:56 ` jamal
2004-12-30 12:34 ` Patrick McHardy
2004-12-30 13:30 ` jamal
2004-12-30 14:16 ` Patrick McHardy
2004-12-30 16:10 ` Patrick McHardy [this message]
2004-12-31 4:45 ` jamal
2004-12-31 9:54 ` Patrick McHardy
2004-12-31 11:26 ` Thomas Graf
2004-12-31 15:00 ` jamal
2004-12-30 22:12 ` Arnaldo Carvalho de Melo
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=41D4286B.1060106@trash.net \
--to=kaber@trash.net \
--cc=hadi@cyberus.ca \
--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).