From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <olteanv@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
f.fainelli@gmail.com, andrew@lunn.ch, vivien.didelot@gmail.com,
vladimir.oltean@nxp.com
Subject: Re: [PATCH net-next 0/2] Ethtool statistics counters cleanup for SJA1105 DSA driver
Date: Fri, 21 May 2021 21:10:10 +0000 [thread overview]
Message-ID: <162163141076.28899.14145976767970780002.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210521131608.4018058-1-olteanv@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 21 May 2021 16:16:06 +0300 you wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> This series removes some reported data from ethtool -S which were not
> counters at all, and reorganizes the code such that counters can be read
> individually and not just all at once.
>
> Vladimir Oltean (2):
> net: dsa: sja1105: stop reporting the queue levels in ethtool port
> counters
> net: dsa: sja1105: don't use burst SPI reads for port statistics
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: dsa: sja1105: stop reporting the queue levels in ethtool port counters
https://git.kernel.org/netdev/net-next/c/30a2e9c0f5cf
- [net-next,2/2] net: dsa: sja1105: don't use burst SPI reads for port statistics
https://git.kernel.org/netdev/net-next/c/039b167d68a3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-05-21 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 13:16 [PATCH net-next 0/2] Ethtool statistics counters cleanup for SJA1105 DSA driver Vladimir Oltean
2021-05-21 13:16 ` [PATCH net-next 1/2] net: dsa: sja1105: stop reporting the queue levels in ethtool port counters Vladimir Oltean
2021-05-21 13:16 ` [PATCH net-next 2/2] net: dsa: sja1105: don't use burst SPI reads for port statistics Vladimir Oltean
2021-05-21 21:10 ` patchwork-bot+netdevbpf [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=162163141076.28899.14145976767970780002.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@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.