From: patchwork-bot+netdevbpf@kernel.org
To: Nihar Chaithanya <niharchaithanya@gmail.com>
Cc: sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
sd@queasysnail.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org
Subject: Re: [PATCH v2] octeontx2-pf: mcs: Remove dead code and semi-colon from rsrc_name()
Date: Tue, 07 Jan 2025 01:00:36 +0000 [thread overview]
Message-ID: <173621163648.3665137.6074342929999257204.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250104171905.13293-1-niharchaithanya@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 4 Jan 2025 22:49:15 +0530 you wrote:
> Every case in the switch-block ends with return statement, and the
> default: branch handles the cases where rsrc_type is invalid and
> returns "Unknown", this makes the return statement at the end of the
> function unreachable and redundant.
> The semi-colon is not required after the switch-block's curly braces.
>
> Remove the semi-colon after the switch-block's curly braces and the
> return statement at the end of the function.
>
> [...]
Here is the summary with links:
- [v2] octeontx2-pf: mcs: Remove dead code and semi-colon from rsrc_name()
https://git.kernel.org/netdev/net-next/c/49afc040f4d7
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-01-07 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 17:19 [PATCH v2] octeontx2-pf: mcs: Remove dead code and semi-colon from rsrc_name() Nihar Chaithanya
2025-01-07 1:00 ` 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=173621163648.3665137.6074342929999257204.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niharchaithanya@gmail.com \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sd@queasysnail.net \
--cc=sgoutham@marvell.com \
--cc=skhan@linuxfoundation.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