From: patchwork-bot+netdevbpf@kernel•org
To: Tobias Waldekranz <tobias@waldekranz•com>
Cc: davem@davemloft•net, kuba@kernel•org, netdev@vger•kernel.org,
andrew@lunn•ch, David.Laight@ACULAB•COM
Subject: Re: [PATCH v3 net-next 0/2] net: dsa: mv88e6xxx: Improve indirect addressing performance
Date: Mon, 31 Jan 2022 11:40:10 +0000 [thread overview]
Message-ID: <164362921094.6327.2899132291555240817.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220128162650.2510062-1-tobias@waldekranz.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft•net>:
On Fri, 28 Jan 2022 17:26:48 +0100 you wrote:
> The individual patches have all the details. This work was triggered
> by recent work on a platform that took 16s (sic) to load the mv88e6xxx
> module.
>
> The first patch gets rid of most of that time by replacing a very long
> delay with a tighter poll loop to wait for the busy bit to clear.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/2] net: dsa: mv88e6xxx: Improve performance of busy bit polling
https://git.kernel.org/netdev/net-next/c/35da1dfd9484
- [v3,net-next,2/2] net: dsa: mv88e6xxx: Improve indirect addressing performance
https://git.kernel.org/netdev/net-next/c/7bca16b22e6a
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-01-31 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 16:26 [PATCH v3 net-next 0/2] net: dsa: mv88e6xxx: Improve indirect addressing performance Tobias Waldekranz
2022-01-28 16:26 ` [PATCH v3 net-next 1/2] net: dsa: mv88e6xxx: Improve performance of busy bit polling Tobias Waldekranz
2022-01-28 17:17 ` Andrew Lunn
2022-01-28 16:26 ` [PATCH v3 net-next 2/2] net: dsa: mv88e6xxx: Improve indirect addressing performance Tobias Waldekranz
2022-01-31 11: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=164362921094.6327.2899132291555240817.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=David.Laight@ACULAB$(echo .)COM \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=tobias@waldekranz$(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