From: Zack Gomez <zack.gomez@gmail.com>
To: leitao@debian.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] netpoll: bound the deferred transmit queue
Date: Fri, 25 Sep 2026 16:19:40 -0400 [thread overview]
Message-ID: <20260925201940.1950809-1-zack.gomez@gmail.com> (raw)
In-Reply-To: <araTwjYJRMlfd2PX@gmail.com>
On Fri, Sep 25, 2026 at 08:32:56AM -0700, Breno Leitao wrote:
> I don't think this should be a fix, honestly. I would prefer to see this
> on net-next without the Fixes tag.
Agreed, I'll drop the tag and send v4 to net-next with your Reviewed-by.
Thanks for the reviews and I'll be watching your patchset as well.
next prev parent reply other threads:[~2026-09-25 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 18:11 [PATCH net v3] netpoll: bound the deferred transmit queue Zack Gomez
2026-09-25 15:32 ` Breno Leitao
2026-09-25 20:19 ` Zack Gomez [this message]
2026-09-27 18:01 ` netdev-bot+sashiko
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=20260925201940.1950809-1-zack.gomez@gmail.com \
--to=zack.gomez@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.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 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.