All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Ayananta Paul <ayanantapaul@gmail.com>
Cc: donald.hunter@gmail.com, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: netlink: fix spelling in tcp_metrics.yaml
Date: Wed, 29 Jul 2026 17:05:52 -0700	[thread overview]
Message-ID: <20260729170552.3c320d1c@kernel.org> (raw)
In-Reply-To: <20260729034147.6970-1-ayanantapaul@gmail.com>

On Wed, 29 Jul 2026 09:11:47 +0530 Ayananta Paul wrote:
> Correct the spelling of "reordering" which was incorrectly
> written as "reodering" on lines 113 and 115.

Unfortunately the uAPI define is also misspelled.
You will need to squash something like this into your patch:

diff --git a/include/uapi/linux/tcp_metrics.h b/include/uapi/linux/tcp_metrics.h
index 927c735a5b0e..74cfb9f7509c 100644
--- a/include/uapi/linux/tcp_metrics.h
+++ b/include/uapi/linux/tcp_metrics.h
@@ -35,7 +35,9 @@ enum {
        TCP_METRICS_A_METRICS_RTTVAR,
        TCP_METRICS_A_METRICS_SSTHRESH,
        TCP_METRICS_A_METRICS_CWND,
-       TCP_METRICS_A_METRICS_REODERING,
+       TCP_METRICS_A_METRICS_REORDERING,
+/* Original spelling had a typo, kept to avoid breaking uAPI */
+#define TCP_METRICS_A_METRICS_REODERING TCP_METRICS_A_METRICS_REORDERING
        TCP_METRICS_A_METRICS_RTT_US,
        TCP_METRICS_A_METRICS_RTTVAR_US,

  parent reply	other threads:[~2026-07-30  0:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  3:41 [PATCH] Documentation: netlink: fix spelling in tcp_metrics.yaml Ayananta Paul
2026-07-29 16:24 ` Joe Damato
2026-07-30  0:05 ` Jakub Kicinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-27 14:46 Ayananta Paul
2026-07-27 17:54 ` Jakub Kicinski

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=20260729170552.3c320d1c@kernel.org \
    --to=kuba@kernel.org \
    --cc=ayanantapaul@gmail.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.