From: jamal <hadi@cyberus.ca>
To: lists@andyfurniss.entadsl.com
Cc: netdev@vger.kernel.org, Stephen Hemminger <shemminger@osdl.org>
Subject: Re: [IPROUTE2]: update documentation on mirred and IFB
Date: Thu, 20 Jul 2006 09:44:28 -0400 [thread overview]
Message-ID: <1153403068.5098.72.camel@jzny2> (raw)
In-Reply-To: <44BED55F.1090405@andyfurniss.entadsl.com>
On Thu, 2006-20-07 at 01:59 +0100, Andy Furniss wrote:
> jamal wrote:
> > About two more or so to complete these..
> >
> > cheers,
> > jamal
> >
> >
> +tc qdisc add dev lo eth0 ?
>
Thanks for catching that Andy. It was attempt at adding ingress to
qdisc. I will wait for Stephen to swallow the other patches and then fix
this - I have at least two more patches to send in that area. Or you can
get a little gitty and send a patch ;->
BTW, if there are areas in the docs, help etc that need clarification
let me know or fix them and send patches. Or if there are better
examples to give send patches.
cheers,
jamal
next prev parent reply other threads:[~2006-07-20 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 12:56 [IPROUTE2]: update documentation on mirred and IFB jamal
2006-07-20 0:59 ` Andy Furniss
2006-07-20 13:44 ` jamal [this message]
2006-08-04 17:49 ` Stephen Hemminger
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=1153403068.5098.72.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=lists@andyfurniss.entadsl.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
/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