All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ziran Zhang <zhangcoder@yeah.net>
Cc: edumazet@google.com, ncardwell@google.com, kuniyu@google.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tcp: clarify comment for mdev_us in struct tcp_sock
Date: Thu, 13 Aug 2026 01:40:13 +0000	[thread overview]
Message-ID: <178658521313.2182080.17382827673130126816.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260805131927.27661-1-zhangcoder@yeah.net>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  5 Aug 2026 21:19:27 +0800 you wrote:
> The existing comment for mdev_us says "medium deviation", but this
> term is inaccurate. The field stores the "mean deviation" of RTT,
> as originally defined in Van Jacobson's paper "Congestion
> Avoidance and Control", and it is scaled by 4 (<< 2) in the Linux
> implementation.
> 
> Update the comment to reflect the correct terminology and storage
> format.
> 
> [...]

Here is the summary with links:
  - tcp: clarify comment for mdev_us in struct tcp_sock
    https://git.kernel.org/netdev/net-next/c/9b20885f1472

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



      parent reply	other threads:[~2026-08-13  1:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 13:19 [PATCH] tcp: clarify comment for mdev_us in struct tcp_sock Ziran Zhang
2026-08-06  8:28 ` Fernando Fernandez Mancera
2026-08-13  1: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=178658521313.2182080.17382827673130126816.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=zhangcoder@yeah.net \
    /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.