netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] tc: add json support to size table
Date: Wed, 23 Nov 2022 06:40:15 +0000	[thread overview]
Message-ID: <166918561519.32105.8295182106645086195.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221123044949.4785-1-stephen@networkplumber.org>

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Tue, 22 Nov 2022 20:49:49 -0800 you wrote:
> Fix the JSON output if size addaption table is used.
> 
> Example:
> [ {
>         "kind": "fq_codel",
>         "handle": "1:",
>         "dev": "enp2s0",
>         "root": true,
>         "refcnt": 2,
>         "options": {
>             "limit": 10240,
>             "flows": 1024,
>             "quantum": 1514,
>             "target": 4999,
>             "interval": 99999,
>             "memory_limit": 33554432,
>             "ecn": true,
>             "drop_batch": 64
>         },
>         "stab": {
>             "overhead": 30,
>             "mpu": 68,
>             "mtu": 2047,
>             "tsize": 512
>         }
>     } ]
> 
> [...]

Here is the summary with links:
  - [iproute2] tc: add json support to size table
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6af6f02cce42

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-11-23  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  4:49 [PATCH iproute2] tc: add json support to size table Stephen Hemminger
2022-11-23  6:40 ` patchwork-bot+netdevbpf [this message]

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=166918561519.32105.8295182106645086195.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).