netdev - Re: [PATCH] tc: man: Fix incorrect parameter format in prio.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120618122546.21ec3267@nehalam.linuxnetplumber.net>
Date:	Mon, 18 Jun 2012 12:25:46 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Li Wei <lw@...fujitsu.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH] tc: man: Fix incorrect parameter format in prio.

On Mon, 18 Jun 2012 14:23:05 +0800
Li Wei <lw@...fujitsu.com> wrote:

> 
> Parameter priomap use blank instead of comma to separate bands,
> update manpage to confirms to this.
> ---
>  man/man8/tc-prio.8 |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/man/man8/tc-prio.8 b/man/man8/tc-prio.8
> index 1625fcc..55a5f3d 100644
> --- a/man/man8/tc-prio.8
> +++ b/man/man8/tc-prio.8
> @@ -11,7 +11,7 @@ major:
>  .B ] prio [ bands 
>  bands
>  .B ] [ priomap
> -band,band,band... 
> +band band band... 
>  .B ] [ estimator 
>  interval timeconstant
>  .B ]
> @@ -134,7 +134,7 @@ showing to which Priority they are mapped.
>  The last column shows the result of the default priomap. On the command line,
>  the default priomap looks like this:
>  
> -    1, 2, 2, 2, 1, 2, 0, 0 , 1, 1, 1, 1, 1, 1, 1, 1
> +    1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
>  
>  This means that priority 4, for example, gets mapped to band number 1.
>  The priomap also allows you to list higher priorities (> 7) which do not

Applied (had to fix whitespace in patch)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html