From: patchwork-bot+netdevbpf@kernel•org
To: Vladimir Oltean <vladimir.oltean@nxp•com>
Cc: netdev@vger•kernel.org, andrew@lunn•ch, f.fainelli@gmail•com,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, netdev@kapio-technology•com, saeed@kernel•org
Subject: Re: [PATCH v2 net-next 0/4] Trace points for mv88e6xxx
Date: Mon, 12 Dec 2022 23:10:16 +0000 [thread overview]
Message-ID: <167088661649.21170.2064571178390062352.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221209172817.371434-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Fri, 9 Dec 2022 19:28:13 +0200 you wrote:
> While testing Hans Schultz' attempt at offloading MAB on mv88e6xxx:
> https://patchwork.kernel.org/project/netdevbpf/cover/20221205185908.217520-1-netdev@kapio-technology.com/
> I noticed that he still didn't get rid of the huge log spam caused by
> ATU and VTU violations, even if we discussed about this:
> https://patchwork.kernel.org/project/netdevbpf/cover/20221112203748.68995-1-netdev@kapio-technology.com/#25091076
>
> It seems unlikely he's going to ever do this, so here is my own stab at
> converting those messages to trace points. This is IMO an improvement
> regardless of whether Hans' work with MAB lands or not, especially the
> VTU violations which were quite annoying to me as well.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/4] net: dsa: mv88e6xxx: remove ATU age out violation print
https://git.kernel.org/netdev/net-next/c/8a1786b7d441
- [v2,net-next,2/4] net: dsa: mv88e6xxx: read FID when handling ATU violations
https://git.kernel.org/netdev/net-next/c/4bf24ad09bc0
- [v2,net-next,3/4] net: dsa: mv88e6xxx: replace ATU violation prints with trace points
https://git.kernel.org/netdev/net-next/c/8646384d80f3
- [v2,net-next,4/4] net: dsa: mv88e6xxx: replace VTU violation prints with trace points
https://git.kernel.org/netdev/net-next/c/9e3d9ae52b56
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:[~2022-12-12 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 17:28 [PATCH v2 net-next 0/4] Trace points for mv88e6xxx Vladimir Oltean
2022-12-09 17:28 ` [PATCH v2 net-next 1/4] net: dsa: mv88e6xxx: remove ATU age out violation print Vladimir Oltean
2022-12-10 0:05 ` Florian Fainelli
2022-12-09 17:28 ` [PATCH v2 net-next 2/4] net: dsa: mv88e6xxx: read FID when handling ATU violations Vladimir Oltean
2022-12-10 0:05 ` Florian Fainelli
2022-12-09 17:28 ` [PATCH v2 net-next 3/4] net: dsa: mv88e6xxx: replace ATU violation prints with trace points Vladimir Oltean
2022-12-09 19:38 ` Saeed Mahameed
2022-12-09 19:40 ` Vladimir Oltean
2022-12-10 0:07 ` Florian Fainelli
2022-12-09 17:28 ` [PATCH v2 net-next 4/4] net: dsa: mv88e6xxx: replace VTU " Vladimir Oltean
2022-12-09 19:39 ` Saeed Mahameed
2022-12-10 0:07 ` Florian Fainelli
2022-12-12 23: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=167088661649.21170.2064571178390062352.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=f.fainelli@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@kapio-technology$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=saeed@kernel$(echo .)org \
--cc=vladimir.oltean@nxp$(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