From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>,
nikolay@cumulusnetworks.com, davem@davemloft.net,
jiri@resnulli.us, ivecera@redhat.com, kuba@kernel.org,
roopa@cumulusnetworks.com, olteanv@gmail.com, andrew@lunn.ch,
UNGLinuxDriver@microchip.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: [PATCH net-next v4 02/11] bridge: mrp: Update Kconfig
Date: Mon, 27 Apr 2020 12:46:47 +0300 [thread overview]
Message-ID: <ea7b30af-57b7-4cad-b73a-a13cf762c742@cogentembedded.com> (raw)
In-Reply-To: <20200426132208.3232-3-horatiu.vultur@microchip.com>
Hello!
On 26.04.2020 16:21, Horatiu Vultur wrote:
> Add the option BRIDGE_MRP to allow to build in or not MRP support.
> The default value is N.
>
> Reviewed-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> net/bridge/Kconfig | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/net/bridge/Kconfig b/net/bridge/Kconfig
> index e4fb050e2078..51a6414145d2 100644
> --- a/net/bridge/Kconfig
> +++ b/net/bridge/Kconfig
> @@ -61,3 +61,15 @@ config BRIDGE_VLAN_FILTERING
> Say N to exclude this support and reduce the binary size.
>
> If unsure, say Y.
> +
> +config BRIDGE_MRP
> + bool "MRP protocol"
> + depends on BRIDGE
> + default n
Not needed, N is the default default. :-)
[...]
MBR, Sergei
next prev parent reply other threads:[~2020-04-27 9:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 13:21 [PATCH net-next v4 00/11] net: bridge: mrp: Add support for Media Redundancy Protocol(MRP) Horatiu Vultur
2020-04-26 13:21 ` [PATCH net-next v4 01/11] bridge: uapi: mrp: Add mrp attributes Horatiu Vultur
2020-04-26 13:21 ` [PATCH net-next v4 02/11] bridge: mrp: Update Kconfig Horatiu Vultur
2020-04-27 9:46 ` Sergei Shtylyov [this message]
2020-04-26 13:22 ` [PATCH net-next v4 03/11] bridge: mrp: Extend bridge interface Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 04/11] net: bridge: Add port attribute IFLA_BRPORT_MRP_RING_OPEN Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 05/11] bridge: mrp: Add MRP interface Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 06/11] switchdev: mrp: Extend switchdev API to offload MRP Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 07/11] bridge: switchdev: mrp: Implement MRP API for switchdev Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 08/11] bridge: mrp: Connect MRP API with the switchdev API Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 09/11] bridge: mrp: Implement netlink interface to configure MRP Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 10/11] bridge: mrp: Integrate MRP into the bridge Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 11/11] net: bridge: Add checks for enabling the STP Horatiu Vultur
2020-04-27 18:40 ` [PATCH net-next v4 00/11] net: bridge: mrp: Add support for Media Redundancy Protocol(MRP) David Miller
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=ea7b30af-57b7-4cad-b73a-a13cf762c742@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=horatiu.vultur@microchip.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=olteanv@gmail.com \
--cc=roopa@cumulusnetworks.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).