From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Victor Nogueira <victor@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next] net_sched: sch_fq: add three drop_reason
Date: Sat, 7 Dec 2024 18:43:52 -0800 [thread overview]
Message-ID: <20241207184352.512e5971@kernel.org> (raw)
In-Reply-To: <20241204171950.89829-1-edumazet@google.com>
On Wed, 4 Dec 2024 17:19:50 +0000 Eric Dumazet wrote:
> Add three new drop_reason, more precise than generic QDISC_DROP:
FTR I applied this a while back, thanks!
--
pw-bot: accept
prev parent reply other threads:[~2024-12-08 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 17:19 [PATCH v2 net-next] net_sched: sch_fq: add three drop_reason Eric Dumazet
2024-12-05 1:07 ` Victor Nogueira
2024-12-05 11:57 ` Toke Høiland-Jørgensen
2024-12-05 12:41 ` Jamal Hadi Salim
2024-12-08 2:43 ` 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=20241207184352.512e5971@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@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;
as well as URLs for NNTP newsgroup(s).