From: patchwork-bot+netdevbpf@kernel.org
To: Adam Ford <aford173@gmail.com>
Cc: netdev@vger.kernel.org, aford@beaconembedded.com,
sergei.shtylyov@gmail.com, davem@davemloft.net, kuba@kernel.org,
robh+dt@kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 1/2] dt-bindings: net: renesas,etheravb: Add additional clocks
Date: Mon, 12 Apr 2021 21:20:10 +0000 [thread overview]
Message-ID: <161826241018.26087.15056633928793158329.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210412132619.7896-1-aford173@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 12 Apr 2021 08:26:18 -0500 you wrote:
> The AVB driver assumes there is an external crystal, but it could
> be clocked by other means. In order to enable a programmable
> clock, it needs to be added to the clocks list and enabled in the
> driver. Since there currently only one clock, there is no
> clock-names list either.
>
> Update bindings to add the additional optional clock, and explicitly
> name both of them.
>
> [...]
Here is the summary with links:
- [V4,1/2] dt-bindings: net: renesas,etheravb: Add additional clocks
https://git.kernel.org/netdev/net-next/c/6f43735b6da6
- [V4,2/2] net: ethernet: ravb: Enable optional refclk
https://git.kernel.org/netdev/net-next/c/8ef7adc6beb2
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-04-12 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 13:26 [PATCH V4 1/2] dt-bindings: net: renesas,etheravb: Add additional clocks Adam Ford
2021-04-12 13:26 ` [PATCH V4 2/2] net: ethernet: ravb: Enable optional refclk Adam Ford
2021-04-13 7:33 ` Geert Uytterhoeven
2021-04-14 13:07 ` Adam Ford
2021-04-14 17:59 ` Geert Uytterhoeven
2021-04-12 21:20 ` 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=161826241018.26087.15056633928793158329.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).