From: Stephen Hemminger <shemminger@vyatta.com>
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, kaber@trash.net
Subject: Re: [iproute2] minor tc cleanup patches
Date: Thu, 21 Jan 2010 10:13:33 -0800 [thread overview]
Message-ID: <20100121101333.515d3d5d@nehalam> (raw)
In-Reply-To: <20100112203428.GA24531@Chamillionaire.breakpoint.cc>
On Tue, 12 Jan 2010 21:34:28 +0100
Florian Westphal <fw@strlen.de> wrote:
> Hello Stephen, hello Patrick,
>
> here are 5 minor patches for iproute2/tc:
> the first two are small man page adjustments.
> The 3rd one makes tc print a more verbose error message instead of -EINVAL.
>
> The 4th is a janitorial patch that removes some stale (c&p) code.
>
> Last patch adds a man page for sched_drr.
> Patrick, it would be nice if you could have a look at this one to see
> if I got everything right (or if i forgot something important).
>
> Thanks a lot!
>
> Alternatively, you may pull from
>
> git://git.breakpoint.cc/fw/iproute2.git cleanups
>
> to obtain the following changes since commit
Applied 1-4 will wait for updated DRR man page for 5
next prev parent reply other threads:[~2010-01-21 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 20:34 [iproute2] minor tc cleanup patches Florian Westphal
2010-01-12 20:39 ` [PATCH 1/5] tc: man: add limit parameter to tc-sfq man page Florian Westphal
2010-01-12 20:43 ` [PATCH 2/5] tc: man: SO_PRIORITY is described in socket documentation, not tc one Florian Westphal
2010-01-12 20:44 ` [PATCH 3/5] tc: red, gred, tbf: more helpful error messages Florian Westphal
2010-01-12 20:45 ` [PATCH 4/5] tc: remove stale code Florian Westphal
2010-01-12 20:45 ` [PATCH 5/5] tc: man: add man page for drr scheduler Florian Westphal
2010-01-13 5:34 ` Patrick McHardy
2010-01-13 8:27 ` Florian Westphal
2010-01-18 22:54 ` [PATCH 5/5 v2] " Florian Westphal
2010-01-21 18:13 ` Stephen Hemminger [this message]
2010-01-21 18:19 ` [iproute2] minor tc cleanup patches Patrick McHardy
2010-01-21 21:51 ` 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=20100121101333.515d3d5d@nehalam \
--to=shemminger@vyatta.com \
--cc=fw@strlen.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.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