From: patchwork-bot+netdevbpf@kernel.org
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
kuba@kernel.org, davem@davemloft.net, tchornyi@marvell.com,
yevhen.orlov@plvision.eu
Subject: Re: [PATCH net-next 1/2] net: marvell: prestera: Fix return value check in prestera_fib_node_find()
Date: Fri, 25 Feb 2022 05:30:11 +0000 [thread overview]
Message-ID: <164576701117.8286.7470592072083909153.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220223084954.1771075-1-yangyingliang@huawei.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 23 Feb 2022 16:49:53 +0800 you wrote:
> rhashtable_lookup_fast() returns NULL pointer not ERR_PTR(), so
> it can return fib_node directly in prestera_fib_node_find().
>
> Fixes: 16de3db1208a ("net: marvell: prestera: add hardware router objects accounting for lpm")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: marvell: prestera: Fix return value check in prestera_fib_node_find()
https://git.kernel.org/netdev/net-next/c/d434ee9dee6d
- [net-next,2/2] net: marvell: prestera: Fix return value check in prestera_kern_fib_cache_find()
https://git.kernel.org/netdev/net-next/c/37f40f81e589
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:[~2022-02-25 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 8:49 [PATCH net-next 1/2] net: marvell: prestera: Fix return value check in prestera_fib_node_find() Yang Yingliang
2022-02-23 8:49 ` [PATCH net-next 2/2] net: marvell: prestera: Fix return value check in prestera_kern_fib_cache_find() Yang Yingliang
2022-02-25 5:30 ` 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=164576701117.8286.7470592072083909153.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tchornyi@marvell.com \
--cc=yangyingliang@huawei.com \
--cc=yevhen.orlov@plvision.eu \
/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.