From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCHv3 0/2] Fix RK3588 error prints
Date: Wed, 12 Apr 2023 08:40:19 +0000 [thread overview]
Message-ID: <168128881909.3903.13367548922290396185.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230407161129.70601-1-sebastian.reichel@collabora.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 7 Apr 2023 18:11:27 +0200 you wrote:
> Hi,
>
> This fixes a couple of false positive error messages printed by stmmac on
> RK3588. I added Fixes tags, but I expect them to go via net-next, since
> the patches are more or less cleanups :)
>
> Changes since PATCHv2:
> * https://lore.kernel.org/all/20230405161043.46190-1-sebastian.reichel@collabora.com/
> * Remove regulator NULL check
> * Switch to devm_clk_bulk_get_optional as suggested by Andrew Lunn
>
> [...]
Here is the summary with links:
- [PATCHv3,1/2] net: ethernet: stmmac: dwmac-rk: rework optional clock handling
https://git.kernel.org/netdev/net-next/c/ea449f7fa0bf
- [PATCHv3,2/2] net: ethernet: stmmac: dwmac-rk: fix optional phy regulator handling
https://git.kernel.org/netdev/net-next/c/db21973263f8
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:[~2023-04-12 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 16:11 Sebastian Reichel
2023-04-07 16:11 ` [PATCHv3 1/2] net: ethernet: stmmac: dwmac-rk: rework optional clock handling Sebastian Reichel
2023-04-07 16:11 ` [PATCHv3 2/2] net: ethernet: stmmac: dwmac-rk: fix optional phy regulator handling Sebastian Reichel
2023-04-12 8: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=168128881909.3903.13367548922290396185.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kernel@collabora.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=sebastian.reichel@collabora.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
all inboxes | Powered by JetHome®