From: patchwork-bot+netdevbpf@kernel.org
To: Ruan Jinjie <ruanjinjie@huawei.com>
Cc: andrew@lunn.ch, simon.horman@corigine.com,
linus.walleij@linaro.org, edumazet@google.com, robh@kernel.org,
f.fainelli@gmail.com, elder@linaro.org, kuba@kernel.org,
pabeni@redhat.com, clement.leger@bootlin.com, kvalo@kernel.org,
bhupesh.sharma@linaro.org, ulli.kroll@googlemail.com,
romieu@fr.zoreil.com, wei.fang@nxp.com,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
dmitry.torokhov@gmail.com, linux-wireless@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, alsi@bang-olufsen.dk,
olteanv@gmail.com, davem@davemloft.net
Subject: Re: [PATCH net-next v3 0/5] net: Remove redundant of_match_ptr() macro
Date: Wed, 16 Aug 2023 09:10:21 +0000 [thread overview]
Message-ID: <169217702147.13419.3048871621351512255.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230814025447.2708620-1-ruanjinjie@huawei.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 14 Aug 2023 10:54:42 +0800 you wrote:
> Since these net drivers depend on CONFIG_OF, there is
> no need to wrap the macro of_match_ptr() here.
>
> Changes in v3:
> - Collect responses from v1 and v2.
>
> Ruan Jinjie (5):
> net: dsa: realtek: Remove redundant of_match_ptr()
> net: dsa: rzn1-a5psw: Remove redundant of_match_ptr()
> net: gemini: Remove redundant of_match_ptr()
> net: qualcomm: Remove redundant of_match_ptr()
> wlcore: spi: Remove redundant of_match_ptr()
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] net: dsa: realtek: Remove redundant of_match_ptr()
https://git.kernel.org/netdev/net-next/c/aae249dfa089
- [net-next,v3,2/5] net: dsa: rzn1-a5psw: Remove redundant of_match_ptr()
https://git.kernel.org/netdev/net-next/c/81d463c02b91
- [net-next,v3,3/5] net: gemini: Remove redundant of_match_ptr()
https://git.kernel.org/netdev/net-next/c/21b566fda00f
- [net-next,v3,4/5] net: qualcomm: Remove redundant of_match_ptr()
https://git.kernel.org/netdev/net-next/c/537a6b992708
- [net-next,v3,5/5] wlcore: spi: Remove redundant of_match_ptr()
https://git.kernel.org/netdev/net-next/c/cf2abd872431
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-08-16 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 2:54 [PATCH net-next v3 0/5] net: Remove redundant of_match_ptr() macro Ruan Jinjie
2023-08-16 9:10 ` 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=169217702147.13419.3048871621351512255.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=bhupesh.sharma@linaro.org \
--cc=clement.leger@bootlin.com \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=edumazet@google.com \
--cc=elder@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=ruanjinjie@huawei.com \
--cc=simon.horman@corigine.com \
--cc=ulli.kroll@googlemail.com \
--cc=wei.fang@nxp.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 NNTP newsgroup(s).