From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Kevin Bracey <kevin@bracey.fi>
Cc: netdev@vger.kernel.org, Kevin Bracey <kevin@bracey.fi>
Subject: Re: [PATCH net-next v2] sch_cake: revise Diffserv docs
Date: Fri, 07 Jan 2022 13:25:29 +0100 [thread overview]
Message-ID: <87czl3ag1y.fsf@toke.dk> (raw)
In-Reply-To: <20220106215637.3132391-1-kevin@bracey.fi>
Kevin Bracey <kevin@bracey.fi> writes:
> Documentation incorrectly stated that CS1 is equivalent to LE for
> diffserv8. But when LE was added to the table, CS1 was pushed into tin
> 1, leaving only LE in tin 0.
>
> Also "TOS1" no longer exists, as that is the same codepoint as LE.
>
> Make other tweaks properly distinguishing codepoints from classes and
> putting current Diffserve codepoints ahead of legacy ones.
>
> Signed-off-by: Kevin Bracey <kevin@bracey.fi>
That's better; thank you for the patch! :)
Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
next prev parent reply other threads:[~2022-01-07 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 20:35 [PATCH net] sch_cake: revise Diffserv docs Kevin Bracey
2022-01-06 20:58 ` Toke Høiland-Jørgensen
2022-01-06 21:56 ` [PATCH net-next v2] " Kevin Bracey
2022-01-07 12:25 ` Toke Høiland-Jørgensen [this message]
2022-01-07 17:00 ` patchwork-bot+netdevbpf
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=87czl3ag1y.fsf@toke.dk \
--to=toke@toke.dk \
--cc=kevin@bracey.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.