From: patchwork-bot+netdevbpf@kernel•org
To: Kurt Kanzenbach <kurt@kmk-computers•de>
Cc: andrew@lunn•ch, vivien.didelot@gmail•com, f.fainelli@gmail•com,
olteanv@gmail•com, davem@davemloft•net, kuba@kernel•org,
netdev@vger•kernel.org
Subject: Re: [PATCH net-next 0/2] net: dsa: hellcreek: Report tables sizes
Date: Tue, 02 Feb 2021 02:40:06 +0000 [thread overview]
Message-ID: <161223360678.28374.6348724450041467252.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210130135934.22870-1-kurt@kmk-computers.de>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sat, 30 Jan 2021 14:59:32 +0100 you wrote:
> Hi,
>
> Florian, Andrew and Vladimir suggested at some point to use devlink for
> reporting tables, features and debugging counters instead of using debugfs and
> printk.
>
> So, start by reporting the VLAN and FDB table sizes.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: dsa: hellcreek: Report VLAN table occupancy
https://git.kernel.org/netdev/net-next/c/7f976d5cf16d
- [net-next,2/2] net: dsa: hellcreek: Report FDB table occupancy
https://git.kernel.org/netdev/net-next/c/8486e83fe1d8
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-02-02 2:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 13:59 [PATCH net-next 0/2] net: dsa: hellcreek: Report tables sizes Kurt Kanzenbach
2021-01-30 13:59 ` [PATCH net-next 1/2] net: dsa: hellcreek: Report VLAN table occupancy Kurt Kanzenbach
2021-01-31 21:31 ` Florian Fainelli
2021-01-30 13:59 ` [PATCH net-next 2/2] net: dsa: hellcreek: Report FDB " Kurt Kanzenbach
2021-01-31 21:32 ` Florian Fainelli
2021-01-31 21:28 ` [PATCH net-next 0/2] net: dsa: hellcreek: Report tables sizes Vladimir Oltean
2021-02-01 16:56 ` Kurt Kanzenbach
2021-02-02 2:40 ` 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=161223360678.28374.6348724450041467252.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kurt@kmk-computers$(echo .)de \
--cc=netdev@vger$(echo .)kernel.org \
--cc=olteanv@gmail$(echo .)com \
--cc=vivien.didelot@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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