Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	vinicius.gomes@intel.com, jhs@mojatatu.com, jiri@resnulli.us
Subject: Re: [PATCH net-next] net: sched: avoid printing uninitialized link speed
Date: Thu, 11 Jun 2026 13:50:06 +0000	[thread overview]
Message-ID: <178118580664.3971116.2333385312602465859.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609183353.1109641-1-kuba@kernel.org>

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue,  9 Jun 2026 11:33:53 -0700 you wrote:
> sch_cbs and sch_taprio print ecmd.base.speed, even if
> netif_get_link_ksettings() failed. When netif_get_link_ksettings()
> fails the ecmd may not be initialized.
> 
> Use the always-initialized speed variable instead.
> The semantics change slightly because UNKNOWN will
> never be printed, but that doesn't seem important
> enough to complicate the code for.
> 
> [...]

Here is the summary with links:
  - [net-next] net: sched: avoid printing uninitialized link speed
    https://git.kernel.org/netdev/net-next/c/518d8d019953

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



      reply	other threads:[~2026-06-11 13:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 18:33 [PATCH net-next] net: sched: avoid printing uninitialized link speed Jakub Kicinski
2026-06-11 13: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=178118580664.3971116.2333385312602465859.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vinicius.gomes@intel.com \
    /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