All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	nikolay@nvidia.com, roopa@nvidia.com,
	jiapeng.chong@linux.alibaba.com, mlxsw@nvidia.com,
	idosch@nvidia.com
Subject: Re: [PATCH net] rtnetlink: Fix regression in bridge VLAN configuration
Date: Wed, 09 Jun 2021 22:00:25 +0000	[thread overview]
Message-ID: <162327602583.7324.14263517606029743607.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210609111753.1739008-1-idosch@idosch.org>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Wed,  9 Jun 2021 14:17:53 +0300 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
> 
> Cited commit started returning errors when notification info is not
> filled by the bridge driver, resulting in the following regression:
> 
>  # ip link add name br1 type bridge vlan_filtering 1
>  # bridge vlan add dev br1 vid 555 self pvid untagged
>  RTNETLINK answers: Invalid argument
> 
> [...]

Here is the summary with links:
  - [net] rtnetlink: Fix regression in bridge VLAN configuration
    https://git.kernel.org/netdev/net/c/d2e381c49636

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



  reply	other threads:[~2021-06-09 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 11:17 [PATCH net] rtnetlink: Fix regression in bridge VLAN configuration Ido Schimmel
2021-06-09 22:00 ` patchwork-bot+netdevbpf [this message]
2021-06-15 17:06 ` Joachim Wiberg

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=162327602583.7324.14263517606029743607.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=idosch@idosch.org \
    --cc=idosch@nvidia.com \
    --cc=jiapeng.chong@linux.alibaba.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=roopa@nvidia.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.