From: patchwork-bot+netdevbpf@kernel.org
To: Colin Foster <colin.foster@in-advantage.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, UNGLinuxDriver@microchip.com,
alexandre.belloni@bootlin.com, claudiu.manoil@nxp.com,
vladimir.oltean@nxp.com
Subject: Re: [PATCH v1 net-next 0/2] clean up ocelot_reset() routine
Date: Thu, 22 Sep 2022 01:40:17 +0000 [thread overview]
Message-ID: <166381081701.5452.11098307943209592493.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220917175127.161504-1-colin.foster@in-advantage.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 17 Sep 2022 10:51:25 -0700 you wrote:
> ocelot_reset() will soon be exported to a common library to be used by
> the ocelot_ext system. This will make error values from regmap calls
> possible, so they must be checked. Additionally, readx_poll_timeout()
> can be substituted for the custom loop, as a simple cleanup.
>
> I don't have hardware to verify this set directly, but there shouldn't
> be any functional changes.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] net: mscc: ocelot: utilize readx_poll_timeout() for chip reset
https://git.kernel.org/netdev/net-next/c/21bb08cd2cda
- [v2,net-next,2/2] net: mscc: ocelot: check return values of writes during reset
https://git.kernel.org/netdev/net-next/c/fa1d90b048c2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-09-22 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 17:51 [PATCH v1 net-next 0/2] clean up ocelot_reset() routine Colin Foster
2022-09-17 17:51 ` [PATCH v2 net-next 1/2] net: mscc: ocelot: utilize readx_poll_timeout() for chip reset Colin Foster
2022-09-17 17:51 ` [PATCH v2 net-next 2/2] net: mscc: ocelot: check return values of writes during reset Colin Foster
2022-09-22 1:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-16 19:13 [PATCH v1 net-next 0/2] clean up ocelot_reset() routine Colin Foster
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=166381081701.5452.11098307943209592493.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox