netdev - Re: [PATCH iproute2 1/2] docs, man: fix some typos

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ttnlo3vh.fsf@nvidia.com>
Date: Wed, 10 Jan 2024 11:35:38 +0100
From: Petr Machata <petrm@...dia.com>
To: Andrea Claudi <aclaudi@...hat.com>
CC: <netdev@...r.kernel.org>, Leon Romanovsky <leon@...nel.org>, Jiri Pirko
	<jiri@...nulli.us>, Jon Maloy <jmaloy@...hat.com>, Stephen Hemminger
	<stephen@...workplumber.org>, David Ahern <dsahern@...il.com>
Subject: Re: [PATCH iproute2 1/2] docs, man: fix some typos


Andrea Claudi <aclaudi@...hat.com> writes:

> Fix some typos and spelling errors in iproute2 documentation.
>
> Signed-off-by: Andrea Claudi <aclaudi@...hat.com>

Reviewed-by: Petr Machata <petrm@...dia.com>

> --- a/doc/actions/actions-general
> +++ b/doc/actions/actions-general
> @@ -116,7 +116,7 @@ The script below does the following:
>  - If it does exceed its rate, its "color" changes to a mark of 2 and it is
>  then passed through a second meter.
>  
> --The second meter is shared across all flows on that device [i am surpised
> +-The second meter is shared across all flows on that device [i am surprised
>  that this seems to be not a well know feature of the policer; Bert was telling
>  me that someone was writing a qdisc just to do sharing across multiple devices;
>  it must be the summer heat again; weve had someone doing that every year around

This document reads more like a newsgroup article or something from a
zine than a formal piece of documentation. Even in this excerpt we see
an uncapitalized "i" and a "weve", and there are many issues like this
elsewhere. Fixing it feels a bit futile, plus I kinda like the
slice-of-history nature of the document :) But yeah, the fix is correct.