From: Jakub Kicinski <kuba@kernel.org>
To: "Hemendra M. Naik" <hemendranaik@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, jiri@resnulli.us,
jhs@mojatatu.com, shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, vishy0777@gmail.com,
tahiliani@nitk.edu.in
Subject: Re: [PATCH net-next v9 0/3] net/sched: sch_fq_pie: add per-flow class statistics
Date: Thu, 1 Oct 2026 17:05:16 -0700 [thread overview]
Message-ID: <20261001170516.592e7f68@kernel.org> (raw)
In-Reply-To: <20260928043358.6866-1-hemendranaik@gmail.com>
On Mon, 28 Sep 2026 10:03:55 +0530 Hemendra M. Naik wrote:
> v9:
> - Add a blank line between structs in commit 1/3.
I wasn't clear - you have to add the new stuff to the YAML spec.
If there's something fundamental that prevents YNL from supporting
sch_fq_pie, please explain. Otherwise you have to fill in the
support for sch_fq_pie and then add your stuff.
This is how we catch up on technical debt in open source world.
--
pw-bot: cr
prev parent reply other threads:[~2026-10-02 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 4:33 [PATCH net-next v9 0/3] net/sched: sch_fq_pie: add per-flow class statistics Hemendra M. Naik
2026-09-28 4:33 ` [PATCH net-next v9 1/3] net/sched: sch_fq_pie: add per-flow statistics via class ops Hemendra M. Naik
2026-09-30 4:34 ` netdev-bot+sashiko
2026-09-28 4:33 ` [PATCH net-next v9 2/3] selftests: tc-testing: add fq_pie per-flow class stats test Hemendra M. Naik
2026-09-30 4:34 ` netdev-bot+sashiko
2026-09-28 4:33 ` [PATCH net-next v9 3/3] net/sched: pie: correct tc_pie_xstats field documentation Hemendra M. Naik
2026-09-30 4:34 ` netdev-bot+sashiko
2026-10-02 0:05 ` Jakub Kicinski [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=20261001170516.592e7f68@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hemendranaik@gmail.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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.