From: patchwork-bot+netdevbpf@kernel.org
To: Luca Weiss <luca@z3ntu.xyz>
Cc: linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, krzysztof.kozlowski@linaro.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 1/2] dt-bindings: nfc: nxp,nci: Document NQ310 compatible
Date: Thu, 01 Dec 2022 05:50:17 +0000 [thread overview]
Message-ID: <166987381777.9213.2696769329913369073.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221128173744.833018-1-luca@z3ntu.xyz>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Nov 2022 18:37:43 +0100 you wrote:
> The NQ310 is another NFC chip from NXP, document the compatible in the
> bindings.
>
> Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> ---
> RESEND to fix Cc
>
> [...]
Here is the summary with links:
- [RESEND,1/2] dt-bindings: nfc: nxp,nci: Document NQ310 compatible
https://git.kernel.org/netdev/net-next/c/a933e7f05bd4
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-12-01 5:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:37 [RESEND PATCH 1/2] dt-bindings: nfc: nxp,nci: Document NQ310 compatible Luca Weiss
2022-11-28 17:37 ` [RESEND PATCH 2/2] arm64: dts: qcom: sdm632-fairphone-fp3: Add NFC Luca Weiss
2022-11-29 13:29 ` Konrad Dybcio
2022-11-29 18:31 ` Luca Weiss
2022-11-30 14:19 ` Konrad Dybcio
2022-11-28 17:46 ` [RESEND PATCH 1/2] dt-bindings: nfc: nxp,nci: Document NQ310 compatible Krzysztof Kozlowski
2022-12-01 5:50 ` patchwork-bot+netdevbpf [this message]
2022-12-28 4:36 ` (subset) " Bjorn Andersson
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=166987381777.9213.2696769329913369073.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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