From: patchwork-bot+netdevbpf@kernel.org
To: Rob Herring <robh@kernel.org>
Cc: krzysztof.kozlowski@linaro.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/2] nfc: mrvl: Move platform_data struct into driver
Date: Thu, 16 Mar 2023 17:50:20 +0000 [thread overview]
Message-ID: <167898902060.2133.11751535560234368439.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230314201309.995421-1-robh@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 14 Mar 2023 15:13:08 -0500 you wrote:
> There are no users of nfcmrvl platform_data struct outside of the
> driver and none will be added, so move it into the driver.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> drivers/nfc/nfcmrvl/nfcmrvl.h | 30 +++++++++++++++--
> include/linux/platform_data/nfcmrvl.h | 48 ---------------------------
> 2 files changed, 28 insertions(+), 50 deletions(-)
> delete mode 100644 include/linux/platform_data/nfcmrvl.h
Here is the summary with links:
- [v2,1/2] nfc: mrvl: Move platform_data struct into driver
https://git.kernel.org/netdev/net-next/c/053fdaa841bd
- [v2,2/2] nfc: mrvl: Use of_property_read_bool() for boolean properties
https://git.kernel.org/netdev/net-next/c/cc6d85c1cb5c
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-03-16 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 20:13 [PATCH v2 1/2] nfc: mrvl: Move platform_data struct into driver Rob Herring
2023-03-14 20:13 ` [PATCH v2 2/2] nfc: mrvl: Use of_property_read_bool() for boolean properties Rob Herring
2023-03-15 14:53 ` [PATCH v2 1/2] nfc: mrvl: Move platform_data struct into driver Simon Horman
2023-03-16 17: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=167898902060.2133.11751535560234368439.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh@kernel.org \
/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