From: patchwork-bot+netdevbpf@kernel.org
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: netdev@vger.kernel.org, horatiu.vultur@microchip.com,
jiri@mellanox.com, f.fainelli@gmail.com, petrm@mellanox.com,
idosch@mellanox.com, davem@davemloft.net, ivecera@redhat.com,
kuba@kernel.org, petrm@nvidia.com
Subject: Re: [PATCH v2 net] net: switchdev: don't set port_obj_info->handled true when -EOPNOTSUPP
Date: Thu, 28 Jan 2021 00:50:10 +0000 [thread overview]
Message-ID: <161179501052.14572.15877029725652969196.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210125124116.102928-1-rasmus.villemoes@prevas.dk>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 25 Jan 2021 13:41:16 +0100 you wrote:
> It's not true that switchdev_port_obj_notify() only inspects the
> ->handled field of "struct switchdev_notifier_port_obj_info" if
> call_switchdev_blocking_notifiers() returns 0 - there's a WARN_ON()
> triggering for a non-zero return combined with ->handled not being
> true. But the real problem here is that -EOPNOTSUPP is not being
> properly handled.
>
> [...]
Here is the summary with links:
- [v2,net] net: switchdev: don't set port_obj_info->handled true when -EOPNOTSUPP
https://git.kernel.org/netdev/net/c/20776b465c0c
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:[~2021-01-28 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 12:41 [PATCH v2 net] net: switchdev: don't set port_obj_info->handled true when -EOPNOTSUPP Rasmus Villemoes
2021-01-28 0: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=161179501052.14572.15877029725652969196.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=idosch@mellanox.com \
--cc=ivecera@redhat.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.com \
--cc=petrm@nvidia.com \
--cc=rasmus.villemoes@prevas.dk \
/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.