From: Florian Westphal <fw@strlen.de>
To: netdev@vger.kernel.org
Cc: shemminger@vyatta.com, Florian Westphal <fw@strlen.de>
Subject: [PATCH 2/5] tc: man: SO_PRIORITY is described in socket documentation, not tc one
Date: Tue, 12 Jan 2010 21:43:19 +0100 [thread overview]
Message-ID: <1263329002-19564-1-git-send-email-fw@strlen.de> (raw)
In-Reply-To: <20100112203428.GA24531@Chamillionaire.breakpoint.cc>
fix up reference: there is no tc(7) man page.
Signed-off-by: Florian Westphal <fw@strlen.de>
---
man/man8/tc-prio.8 | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/man/man8/tc-prio.8 b/man/man8/tc-prio.8
index 780bcd5..1625fcc 100644
--- a/man/man8/tc-prio.8
+++ b/man/man8/tc-prio.8
@@ -50,7 +50,7 @@ be enqueued.
From userspace
A process with sufficient privileges can encode the destination class
directly with SO_PRIORITY, see
-.BR tc(7).
+.BR socket(7).
.TP
with a tc filter
A tc filter attached to the root qdisc can point traffic directly to a class
--
1.6.4.4
next prev parent reply other threads:[~2010-01-12 20:44 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 ` Florian Westphal [this message]
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 ` [iproute2] minor tc cleanup patches Stephen Hemminger
2010-01-21 18:19 ` 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=1263329002-19564-1-git-send-email-fw@strlen.de \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).