From: Cong Wang <xiyou.wangcong@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, Simon Horman <horms@kernel.org>
Subject: Re: [ANN] netdev foundation TSC meeting notes - Nov 25th
Date: Wed, 26 Nov 2025 20:24:24 -0800 [thread overview]
Message-ID: <aSfSeHUtMuJt6uEV@pop-os.localdomain> (raw)
In-Reply-To: <20251126141700.25c097cb@kernel.org>
Hi Jakub,
On Wed, Nov 26, 2025 at 02:17:00PM -0800, Jakub Kicinski wrote:
>
> LPC: should we have a “maintainer talk / Q&A”? 30min in the AM?
> - Will hold before official start at 10am
> - Paolo will “squash” schedule into remaining time
>
Yes, please. I will bring up the concern of knowingly breaking valid
use case of netem Qdisc recently:
https://lore.kernel.org/netdev/20251110123807.07ff5d89@phoenix/
https://lore.kernel.org/all/aG10rqwjX6elG1Gx@pop-os.localdomain/#t
Looking forward to talking to you in person at LPC.
Thanks!
Cong
prev parent reply other threads:[~2025-11-27 4:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 22:17 [ANN] netdev foundation TSC meeting notes - Nov 25th Jakub Kicinski
2025-11-27 4:24 ` Cong Wang [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=aSfSeHUtMuJt6uEV@pop-os.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).