From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40pengutronix=2Ede=3E?=@ci.codeaurora.org
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de
Subject: Re: [PATCH 1/2] net: stmmac: Make stmmac_dvr_remove() return void
Date: Tue, 14 Feb 2023 04:10:18 +0000 [thread overview]
Message-ID: <167634781860.18399.10618008698033755860.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230211112431.214252-1-u.kleine-koenig@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 11 Feb 2023 12:24:30 +0100 you wrote:
> The function returns zero unconditionally. Change it to return void instead
> which simplifies some callers as error handing becomes unnecessary.
>
> This also makes it more obvious that most platform remove callbacks always
> return zero.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>
> [...]
Here is the summary with links:
- [1/2] net: stmmac: Make stmmac_dvr_remove() return void
https://git.kernel.org/netdev/net-next/c/ff0011cf5601
- [2/2] net: stmmac: dwc-qos: Make struct dwc_eth_dwmac_data::remove return void
https://git.kernel.org/netdev/net-next/c/1a940b00013a
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-02-14 4:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 11:24 [PATCH 1/2] net: stmmac: Make stmmac_dvr_remove() return void Uwe Kleine-König
2023-02-11 11:24 ` [PATCH 2/2] net: stmmac: dwc-qos: Make struct dwc_eth_dwmac_data::remove " Uwe Kleine-König
2023-02-13 14:21 ` [PATCH 1/2] net: stmmac: Make stmmac_dvr_remove() " Larysa Zaremba
2023-02-13 16:23 ` Uwe Kleine-König
2023-02-14 1:36 ` Jakub Kicinski
2023-02-14 4: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=167634781860.18399.10618008698033755860.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40pengutronix=2Ede=3E?=@ci.codeaurora.org \
--cc=alexandre.torgue@foss.st.com \
--cc=joabreu@synopsys.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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).