From: patchwork-bot+netdevbpf@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH 1/2] net: dsa: microchip: drop driver owner assignment
Date: Wed, 03 Apr 2024 01:40:34 +0000 [thread overview]
Message-ID: <171210843475.14193.13174868089209942320.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240330211023.100924-1-krzysztof.kozlowski@linaro.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 30 Mar 2024 22:10:22 +0100 you wrote:
> Core in spi_register_driver() already sets the .owner, so driver
> does not need to.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> drivers/net/dsa/microchip/ksz_spi.c | 1 -
> 1 file changed, 1 deletion(-)
Here is the summary with links:
- [net-next,1/2] net: dsa: microchip: drop driver owner assignment
https://git.kernel.org/netdev/net-next/c/a343eb0343e5
- [net-next,2/2] net: dsa: sja1105: drop driver owner assignment
https://git.kernel.org/netdev/net-next/c/ad6afdfc638a
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:[~2024-04-03 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 21:10 [net-next PATCH 1/2] net: dsa: microchip: drop driver owner assignment Krzysztof Kozlowski
2024-03-30 21:10 ` Krzysztof Kozlowski
2024-03-30 21:10 ` [net-next PATCH 2/2] net: dsa: sja1105: " Krzysztof Kozlowski
2024-03-30 21:10 ` Krzysztof Kozlowski
2024-03-30 21:10 ` Krzysztof Kozlowski
2024-04-02 8:32 ` Simon Horman
2024-04-02 12:46 ` Florian Fainelli
2024-04-02 8:32 ` [net-next PATCH 1/2] net: dsa: microchip: " Simon Horman
2024-04-02 12:45 ` Florian Fainelli
2024-04-03 1:40 ` 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=171210843475.14193.13174868089209942320.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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).