From: Vladimir Oltean <olteanv@gmail.com>
To: patchwork-bot+netdevbpf@kernel.org, davem@davemloft.net
Cc: kuba@kernel.org, netdev@vger.kernel.org, f.fainelli@gmail.com,
andrew@lunn.ch, vivien.didelot@gmail.com, kurt@linutronix.de,
woojung.huh@microchip.com, linus.walleij@linaro.org,
hauke@hauke-m.de, jiri@resnulli.us, ivecera@redhat.com,
roopa@nvidia.com, nikolay@nvidia.com, dqfext@gmail.com,
idosch@idosch.org
Subject: Re: [PATCH net-next 0/5] Propagate extack for switchdev VLANs from DSA
Date: Mon, 15 Feb 2021 22:49:22 +0200 [thread overview]
Message-ID: <20210215204922.p35mczveuoagpg3i@skbuf> (raw)
In-Reply-To: <161342160865.4070.3346635751399377653.git-patchwork-notify@kernel.org>
On Mon, Feb 15, 2021 at 08:40:08PM +0000, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
>
> This series was applied to netdev/net-next.git (refs/heads/master):
>
> On Sat, 13 Feb 2021 22:43:14 +0200 you wrote:
> > From: Vladimir Oltean <vladimir.oltean@nxp.com>
> >
> > This series moves the restriction messages printed by the DSA core, and
> > by some individual device drivers, into the netlink extended ack
> > structure, to be communicated to user space where possible, or still
> > printed to the kernel log from the bridge layer.
> >
> > [...]
>
> Here is the summary with links:
> - [net-next,1/5] net: bridge: remove __br_vlan_filter_toggle
> https://git.kernel.org/netdev/net-next/c/7a572964e0c4
> - [net-next,2/5] net: bridge: propagate extack through store_bridge_parm
> https://git.kernel.org/netdev/net-next/c/9e781401cbfc
> - [net-next,3/5] net: bridge: propagate extack through switchdev_port_attr_set
> https://git.kernel.org/netdev/net-next/c/dcbdf1350e33
> - [net-next,4/5] net: dsa: propagate extack to .port_vlan_add
> https://git.kernel.org/netdev/net-next/c/31046a5fd92c
> - [net-next,5/5] net: dsa: propagate extack to .port_vlan_filtering
> https://git.kernel.org/netdev/net-next/c/89153ed6ebc1
>
> You are awesome, thank you!
> --
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
Ouch, I wasn't expecting you to merge these patches.
I had told Nikolay in patch 3 that I was going to resend after the merge window:
https://patchwork.kernel.org/project/netdevbpf/patch/20210213204319.1226170-4-olteanv@gmail.com/
Nonetheless, since there's going to be a short window of build breakage
in net-next when CONFIG_SWITCHDEV=n and/or CONFIG_BRIDGE_VLAN_FILTERING=n
regardless of whether you revert the series now or wait a bit, can I
just send the fixup patch for the function prototypes? Shouldn't take me
more than 15 minutes or so.
prev parent reply other threads:[~2021-02-15 20:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 20:43 [PATCH net-next 0/5] Propagate extack for switchdev VLANs from DSA Vladimir Oltean
2021-02-13 20:43 ` [PATCH net-next 1/5] net: bridge: remove __br_vlan_filter_toggle Vladimir Oltean
2021-02-14 1:04 ` Florian Fainelli
2021-02-14 10:20 ` Nikolay Aleksandrov
2021-02-13 20:43 ` [PATCH net-next 2/5] net: bridge: propagate extack through store_bridge_parm Vladimir Oltean
2021-02-14 1:06 ` Florian Fainelli
2021-02-14 10:43 ` Nikolay Aleksandrov
2021-02-13 20:43 ` [PATCH net-next 3/5] net: bridge: propagate extack through switchdev_port_attr_set Vladimir Oltean
2021-02-14 1:14 ` Florian Fainelli
2021-02-14 10:45 ` Nikolay Aleksandrov
2021-02-14 16:39 ` Vladimir Oltean
2021-02-13 20:43 ` [PATCH net-next 4/5] net: dsa: propagate extack to .port_vlan_add Vladimir Oltean
2021-02-14 1:16 ` Florian Fainelli
2021-02-13 20:43 ` [PATCH net-next 5/5] net: dsa: propagate extack to .port_vlan_filtering Vladimir Oltean
2021-02-14 1:17 ` Florian Fainelli
2021-02-15 20:40 ` [PATCH net-next 0/5] Propagate extack for switchdev VLANs from DSA patchwork-bot+netdevbpf
2021-02-15 20:49 ` Vladimir Oltean [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=20210215204922.p35mczveuoagpg3i@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=idosch@idosch.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linus.walleij@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=roopa@nvidia.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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.