From: patchwork-bot+netdevbpf@kernel.org
To: Yingjie Wang <wangyingjie55@126.com>
Cc: davem@davemloft.net, kuba@kernel.org, vraman@marvell.com,
skardach@marvell.com, sgoutham@marvell.com, lcherian@marvell.com,
gakula@marvell.com, jerinj@marvell.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] octeontx2-af: Fix missing check bugs in rvu_cgx.c
Date: Fri, 15 Jan 2021 19:40:08 +0000 [thread overview]
Message-ID: <161073960808.5378.10488625223498492105.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1610719804-35230-1-git-send-email-wangyingjie55@126.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 15 Jan 2021 06:10:04 -0800 you wrote:
> From: Yingjie Wang <wangyingjie55@126.com>
>
> In rvu_mbox_handler_cgx_mac_addr_get()
> and rvu_mbox_handler_cgx_mac_addr_set(),
> the msg is expected only from PFs that are mapped to CGX LMACs.
> It should be checked before mapping,
> so we add the is_cgx_config_permitted() in the functions.
>
> [...]
Here is the summary with links:
- [v3] octeontx2-af: Fix missing check bugs in rvu_cgx.c
https://git.kernel.org/netdev/net/c/b7ba6cfabc42
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-01-15 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 14:10 [PATCH v3] octeontx2-af: Fix missing check bugs in rvu_cgx.c wangyingjie55
2021-01-15 19:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-15 13:26 wangyingjie55
2021-01-14 5:30 wangyingjie55
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=161073960808.5378.10488625223498492105.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgoutham@marvell.com \
--cc=skardach@marvell.com \
--cc=vraman@marvell.com \
--cc=wangyingjie55@126.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).