All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dan Carpenter <error27@gmail.com>
Cc: davem@davemloft.net, steen.hegelund@microchip.com,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	lars.povlsen@microchip.com, daniel.machon@microchip.com,
	UNGLinuxDriver@microchip.com, casper.casan@gmail.com,
	netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net-next] net: microchip: sparx5: fix uninitialized variables
Date: Tue, 22 Nov 2022 04:50:15 +0000	[thread overview]
Message-ID: <166909261582.32298.17891541863341490595.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Y3eg9Ml/LmLR3L3C@kili>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 18 Nov 2022 18:12:52 +0300 you wrote:
> Smatch complains that "err" can be uninitialized on these paths.  Also
> it's just nicer to "return 0;" instead of "return err;"
> 
> Fixes: 3a344f99bb55 ("net: microchip: sparx5: Add support for TC flower ARP dissector")
> Signed-off-by: Dan Carpenter <error27@gmail.com>
> ---
>  drivers/net/ethernet/microchip/sparx5/sparx5_tc_flower.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)

Here is the summary with links:
  - [net-next] net: microchip: sparx5: fix uninitialized variables
    https://git.kernel.org/netdev/net-next/c/4e9a61394dc4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-11-22  4:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 15:12 [PATCH net-next] net: microchip: sparx5: fix uninitialized variables Dan Carpenter
2022-11-22  4:50 ` 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=166909261582.32298.17891541863341490595.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=casper.casan@gmail.com \
    --cc=daniel.machon@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=error27@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=lars.povlsen@microchip.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steen.hegelund@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.