From: patchwork-bot+netdevbpf@kernel•org
To: Vladimir Oltean <vladimir.oltean@nxp•com>
Cc: netdev@vger•kernel.org, dsahern@kernel•org,
stephen@networkplumber•org, vinicius.gomes@intel•com
Subject: Re: [PATCH v2 iproute2 1/2] tc/taprio: don't print netlink attributes which weren't reported by the kernel
Date: Wed, 09 Aug 2023 20:50:20 +0000 [thread overview]
Message-ID: <169161422083.352.17536032995311163536.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230807220936.4164355-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber•org>:
On Tue, 8 Aug 2023 01:09:35 +0300 you wrote:
> When an admin schedule is pending and hasn't yet become operational, the
> kernel will report only the parameters of the admin schedule in a nested
> TCA_TAPRIO_ATTR_ADMIN_SCHED attribute.
>
> However, we default to printing zeroes even for the parameters of the
> operational base time, when that doesn't exist.
>
> [...]
Here is the summary with links:
- [v2,iproute2,1/2] tc/taprio: don't print netlink attributes which weren't reported by the kernel
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=a5f695cbb130
- [v2,iproute2,2/2] tc/taprio: fix JSON output when TCA_TAPRIO_ATTR_ADMIN_SCHED is present
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=f848310a7279
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-09 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 22:09 [PATCH v2 iproute2 1/2] tc/taprio: don't print netlink attributes which weren't reported by the kernel Vladimir Oltean
2023-08-07 22:09 ` [PATCH v2 iproute2 2/2] tc/taprio: fix JSON output when TCA_TAPRIO_ATTR_ADMIN_SCHED is present Vladimir Oltean
2023-08-09 20:50 ` 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=169161422083.352.17536032995311163536.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=dsahern@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
--cc=vinicius.gomes@intel$(echo .)com \
--cc=vladimir.oltean@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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