All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Hemendra M. Naik" <hemendranaik@gmail.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, jhs@mojatatu.com,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	vishy0777@gmail.com, tahiliani@nitk.edu.in
Subject: Re: [PATCH iproute2-next v6 3/3] tc: correct tc_pie_xstats field documentation
Date: Mon, 21 Sep 2026 11:19:24 -0700	[thread overview]
Message-ID: <20260921111924.2cd405de@phoenix.local> (raw)
In-Reply-To: <20260919061254.39678-4-hemendranaik@gmail.com>

On Sat, 19 Sep 2026 11:42:54 +0530
"Hemendra M. Naik" <hemendranaik@gmail.com> wrote:

> Correct the comments describing the delay and avg_dq_rate fields in
> struct tc_pie_xstats to match the values exported by the kernel.
> 
> Update the documented units for delay from milliseconds to
> microseconds, and for avg_dq_rate from bits/pie_time to
> bytes/second.
> 
> These are documentation-only changes and do not affect the UAPI or
> runtime behavior.
> 
> Signed-off-by: Hemendra M. Naik <hemendranaik@gmail.com>
> Signed-off-by: Vishal Kamath <vishy0777@gmail.com>
> Signed-off-by: Mohit P. Tahiliani <tahiliani@nitk.edu.in>
> ---

Header file changes are done by getting patch accepted to kernel.
Then the headers generated by "make headers_install" are synced
with iproute2. We don't take changes directly.

      reply	other threads:[~2026-09-21 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19  6:12 [PATCH iproute2-next v6 0/3] tc: fq_pie: add per-flow class statistics support Hemendra M. Naik
2026-09-19  6:12 ` [PATCH iproute2-next v6 1/3] tc: fq_pie: add support for printing per-flow PIE statistics Hemendra M. Naik
2026-09-19  6:12 ` [PATCH iproute2-next v6 2/3] tc: pie: print avg_dq_rate in human-readable format Hemendra M. Naik
2026-09-19  6:12 ` [PATCH iproute2-next v6 3/3] tc: correct tc_pie_xstats field documentation Hemendra M. Naik
2026-09-21 18:19   ` Stephen Hemminger [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=20260921111924.2cd405de@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=hemendranaik@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tahiliani@nitk.edu.in \
    --cc=vishy0777@gmail.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.