From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
Cc: sean.wang@mediatek.com, Landen.Chao@mediatek.com, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
matthias.bgg@gmail.com, p.zabel@pengutronix.de,
linux@armlinux.org.uk, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next,v2] net: dsa: mt7530: clean up core and TRGMII clock setup
Date: Mon, 29 Mar 2021 01:00:11 +0000 [thread overview]
Message-ID: <161697961139.31306.12191866785096357875.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210327060752.474627-1-ilya.lipnitskiy@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 26 Mar 2021 23:07:52 -0700 you wrote:
> Three minor changes:
>
> - When disabling PLL, there is no need to call core_write_mmd_indirect
> directly, use the core_write wrapper instead like the rest of the code
> in the function does. This change helps with consistency and
> readability. Move the comment to the definition of
> core_read_mmd_indirect where it belongs.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: dsa: mt7530: clean up core and TRGMII clock setup
https://git.kernel.org/netdev/net-next/c/4732315ca9fe
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-03-29 1:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 5:55 [PATCH net-next] " Ilya Lipnitskiy
2021-03-27 6:07 ` [PATCH net-next,v2] " Ilya Lipnitskiy
2021-03-27 14:45 ` Andrew Lunn
2021-03-29 1:00 ` 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=161697961139.31306.12191866785096357875.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Landen.Chao@mediatek.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=ilya.lipnitskiy@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@gmail.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®