From: patchwork-bot+netdevbpf@kernel.org
To: Stephan Gerhold <stephan@gerhold.net>
Cc: krzysztof.kozlowski@canonical.com, davem@davemloft.net,
kuba@kernel.org, k.opasiak@samsung.com, robh+dt@kernel.org,
linux-nfc@lists.01.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bongsu.jeon@samsung.com, ~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v2 1/2] dt-bindings: net: nfc: s3fwrn5: Add optional clock
Date: Wed, 19 May 2021 19:50:10 +0000 [thread overview]
Message-ID: <162145381019.1870.2964109189084564601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210519091613.7343-1-stephan@gerhold.net>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 19 May 2021 11:16:12 +0200 you wrote:
> On some systems, S3FWRN5 depends on having an external clock enabled
> to function correctly. Allow declaring that clock in the device tree.
>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
> Changes in v2: Minor change in commit message only
> v1: https://lore.kernel.org/netdev/20210518133935.571298-1-stephan@gerhold.net/
>
> [...]
Here is the summary with links:
- [v2,1/2] dt-bindings: net: nfc: s3fwrn5: Add optional clock
https://git.kernel.org/netdev/net-next/c/9cc52f5a533a
- [v2,2/2] nfc: s3fwrn5: i2c: Enable optional clock from device tree
https://git.kernel.org/netdev/net-next/c/340f42f7ff0b
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-05-19 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 9:16 [PATCH v2 1/2] dt-bindings: net: nfc: s3fwrn5: Add optional clock Stephan Gerhold
2021-05-19 9:16 ` [PATCH v2 2/2] nfc: s3fwrn5: i2c: Enable optional clock from device tree Stephan Gerhold
2021-05-19 16:13 ` [linux-nfc] " Krzysztof Kozlowski
2021-05-19 15:59 ` [linux-nfc] [PATCH v2 1/2] dt-bindings: net: nfc: s3fwrn5: Add optional clock Krzysztof Kozlowski
2021-05-19 19:50 ` 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=162145381019.1870.2964109189084564601.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bongsu.jeon@samsung.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=k.opasiak@samsung.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 NNTP newsgroup(s).