From: "Hemendra M. Naik" <hemendranaik@gmail.com>
To: kuba@kernel.org
Cc: davem@davemloft.net, edumazet@google.com, hemendranaik@gmail.com,
horms@kernel.org, jhs@mojatatu.com, jiri@resnulli.us,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, shuah@kernel.org,
tahiliani@nitk.edu.in, vishy0777@gmail.com
Subject: Re: [PATCH net-next v6 0/3] net/sched: sch_fq_pie: add per-flow class statistics
Date: Wed, 23 Sep 2026 09:31:36 +0530 [thread overview]
Message-ID: <20260923040136.13432-1-hemendranaik@gmail.com> (raw)
In-Reply-To: <20260922180458.5c54ebb8@kernel.org>
Hi Jakub,
We have vendored the temporary UAPI header changes into the GitHub
development branch (https://github.com/H-N41K/iproute2-next/tree/fq_pie_class_stats/)
as requested, so it should now build standalone in your CI pipeline.
Please note that this header sync commit is not present in the official
iproute2 patch submitted to the mailing list
(https://lore.kernel.org/netdev/20260922211139.38570-1-hemendranaik@gmail.com/).
It was added to the GitHub branch strictly for validation and testing purposes.
Regards,
Hemendra
prev parent reply other threads:[~2026-09-23 4:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 20:42 Hemendra M. Naik
2026-09-17 20:42 ` [PATCH net-next v6 1/3] net/sched: sch_fq_pie: add per-flow statistics via class ops Hemendra M. Naik
2026-09-21 20:43 ` netdev-bot+sashiko
2026-09-22 20:20 ` Hemendra M. Naik
2026-09-17 20:42 ` [PATCH net-next v6 2/3] selftests: tc-testing: add fq_pie per-flow class stats test Hemendra M. Naik
2026-09-21 20:43 ` netdev-bot+sashiko
2026-09-22 20:26 ` Hemendra M. Naik
2026-09-17 20:42 ` [PATCH net-next v6 3/3] net/sched: pie: correct tc_pie_xstats field documentation Hemendra M. Naik
2026-09-21 20:43 ` netdev-bot+sashiko
2026-09-22 20:30 ` Hemendra M. Naik
2026-09-18 22:59 ` [PATCH net-next v6 0/3] net/sched: sch_fq_pie: add per-flow class statistics Jakub Kicinski
2026-09-19 6:26 ` Hemendra M. Naik
2026-09-23 1:04 ` Jakub Kicinski
2026-09-23 4:01 ` Hemendra M. Naik [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=20260923040136.13432-1-hemendranaik@gmail.com \
--to=hemendranaik@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®