From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <olteanv@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
f.fainelli@gmail.com, kurt@linutronix.de, vkochan@marvell.com,
tchornyi@marvell.com, idosch@nvidia.com,
clang-built-linux@googlegroups.com, linux-mm@kvack.org,
kbuild-all@lists.01.org
Subject: Re: [PATCH net-next] net: marvell: prestera: fix uninitialized vid in prestera_port_vlans_add
Date: Fri, 15 Jan 2021 00:50:08 +0000 [thread overview]
Message-ID: <161067180848.3913.16168009401254422093.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210114083556.2274440-1-olteanv@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Thu, 14 Jan 2021 10:35:56 +0200 you wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> prestera_bridge_port_vlan_add should have been called with vlan->vid,
> however this was masked by the presence of the local vid variable and I
> did not notice the build warning.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Fixes: b7a9e0da2d1c ("net: switchdev: remove vid_begin -> vid_end range from VLAN objects")
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> [...]
Here is the summary with links:
- [net-next] net: marvell: prestera: fix uninitialized vid in prestera_port_vlans_add
https://git.kernel.org/netdev/net-next/c/c612fe780803
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 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 8:35 [PATCH net-next] net: marvell: prestera: fix uninitialized vid in prestera_port_vlans_add Vladimir Oltean
2021-01-14 18:48 ` Florian Fainelli
2021-01-14 18:48 ` Florian Fainelli
2021-01-14 21:46 ` Taras
2021-01-14 21:46 ` Taras Chornyi [C]
2021-01-15 0:50 ` patchwork-bot+netdevbpf [this message]
2021-01-15 0:50 ` patchwork-bot+netdevbpf
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=161067180848.3913.16168009401254422093.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=idosch@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=tchornyi@marvell.com \
--cc=vkochan@marvell.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.