All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Ovidiu Panait <ovidiu.panait.rb@renesas.com>,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	pabeni@redhat.com, mcoquelin.stm32@gmail.com,
	alexandre.torgue@foss.st.com, xiaoliang.yang_1@nxp.com,
	netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: stmmac: Track and report the TX DMA threshold per queue
Date: Tue, 20 Oct 2026 15:29:22 -0700	[thread overview]
Message-ID: <20261020152922.4d06ad30@kernel.org> (raw)
In-Reply-To: <466cff3f-e3bb-4581-9e79-f4a980570244@bootlin.com>

On Tue, 13 Oct 2026 14:44:43 +0200 Maxime Chevallier wrote:
> That's a nice cleanup, thanks for addressing it :)
> 
> Patch 2 belongs to net-next though, it's not a fix and it brings some user-visible
> changes in the stats.

True. Given the merge window started, tho, I'm just going to apply this
series to net-next in one go.


  reply	other threads:[~2026-10-20 22:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 11:45 [PATCH net 0/2] net: stmmac: Track and report the TX DMA threshold per queue Ovidiu Panait
2026-10-13 11:45 ` [PATCH net 1/2] net: stmmac: Track " Ovidiu Panait
2026-10-13 12:45   ` Maxime Chevallier
2026-10-13 11:45 ` [PATCH net 2/2] net: stmmac: Report " Ovidiu Panait
2026-10-13 12:44 ` [PATCH net 0/2] net: stmmac: Track and report " Maxime Chevallier
2026-10-20 22:29   ` Jakub Kicinski [this message]
2026-10-21  0:10 ` patchwork-bot+netdevbpf

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=20261020152922.4d06ad30@kernel.org \
    --to=kuba@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ovidiu.panait.rb@renesas.com \
    --cc=pabeni@redhat.com \
    --cc=xiaoliang.yang_1@nxp.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.