From: patchwork-bot+netdevbpf@kernel.org
To: Markus Elfring <Markus.Elfring@web.de>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
andrew+netdev@lunn.ch, byungchul@sk.com, davem@davemloft.net,
diogo.ivo@siemens.com, edumazet@google.com,
grygorii.strashko@ti.com, h-mittal1@ti.com, kuba@kernel.org,
jan.kiszka@siemens.com, krzysztof.kozlowski@linaro.org,
danishanwar@ti.com, m-malladi@ti.com, pabeni@redhat.com,
r-gunasekaran@ti.com, rogerq@kernel.org, horms@kernel.org,
vigneshr@ti.com, linux-kernel@vger.kernel.org,
linux.amoon@gmail.com, christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH net-next] net: ti: icssg-prueth: Omit a variable reassignment in prueth_netdev_init()
Date: Thu, 23 Oct 2025 09:40:06 +0000 [thread overview]
Message-ID: <176121240626.2969431.4409960503973897261.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <71f7daa3-d4f4-4753-aae8-67040fc8297d@web.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 20 Oct 2025 16:02:56 +0200 you wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Mon, 20 Oct 2025 15:46:11 +0200
>
> An error code was assigned to a variable and checked accordingly.
> This value was passed to a dev_err_probe() call in an if branch.
> This function is documented in the way that the same value is returned.
> Thus delete two redundant variable reassignments.
>
> [...]
Here is the summary with links:
- [net-next] net: ti: icssg-prueth: Omit a variable reassignment in prueth_netdev_init()
https://git.kernel.org/netdev/net-next/c/e0665df8c501
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:[~2025-10-23 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 14:02 [PATCH net-next] net: ti: icssg-prueth: Omit a variable reassignment in prueth_netdev_init() Markus Elfring
2025-10-20 15:51 ` Alexander Lobakin
2025-10-23 9: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=176121240626.2969431.4409960503973897261.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=andrew+netdev@lunn.ch \
--cc=byungchul@sk.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=grygorii.strashko@ti.com \
--cc=h-mittal1@ti.com \
--cc=horms@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=m-malladi@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=rogerq@kernel.org \
--cc=vigneshr@ti.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).