From: Vladimir Oltean <olteanv@gmail.com>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: Ivan Vecera <ivecera@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, Petr Machata <petrm@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
bridge@lists.linux-foundation.org,
Russell King <linux@armlinux.org.uk>,
Vivien Didelot <vivien.didelot@gmail.com>,
Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, Cooper Lees <me@cooperlees.com>,
Roopa Prabhu <roopa@nvidia.com>,
kuba@kernel.org, Matt Johnston <matt@codeconstruct.com.au>,
davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: [Bridge] [PATCH v4 net-next 10/15] net: dsa: Validate hardware support for MST
Date: Wed, 16 Mar 2022 15:03:49 +0200 [thread overview]
Message-ID: <20220316130349.kmjonrhsx7upj55h@skbuf> (raw)
In-Reply-To: <8735jil0m1.fsf@waldekranz.com>
On Wed, Mar 16, 2022 at 10:15:18AM +0100, Tobias Waldekranz wrote:
> >> +int dsa_port_mst_enable(struct dsa_port *dp, bool on,
> >> + struct netlink_ext_ack *extack)
> >> +{
> >> + if (!on)
> >> + return 0;
> >> +
> >> + if (!dsa_port_supports_mst(dp)) {
> >> + NL_SET_ERR_MSG_MOD(extack, "Hardware does not support MST");
> >> + return -EINVAL;
> >> + }
> >> +
> >> + return 0;
> >> +}
> >
> > Experimenting a bit... maybe this looks tidier? We make the "if" condition
> > have the same basic structure as the previous "if (br_mst_enabled(br) &&
> > !dsa_port_supports_mst(dp))", albeit transformed using De Morgan's rules.
> >
> > {
> > if (!on || dsa_port_supports_mst(dp))
> > return 0;
> >
> > NL_SET_ERR_MSG_MOD(extack, "Hardware does not support MST");
> > return -EINVAL;
> > }
>
> I initially had it like this. It looks tidier, yes - but to me the
> intent is less obvious when reading it. How about:
>
> {
> if (on && !dsa_port_supports_mst(dp)) {
> NL_SET_ERR_MSG_MOD(extack, "Hardware does not support MST");
> return -EINVAL;
> }
>
> return 0;
> }
Yes, let's go with this.
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Oltean <olteanv@gmail.com>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, Ivan Vecera <ivecera@redhat.com>,
Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Russell King <linux@armlinux.org.uk>,
Petr Machata <petrm@nvidia.com>, Ido Schimmel <idosch@nvidia.com>,
Matt Johnston <matt@codeconstruct.com.au>,
Cooper Lees <me@cooperlees.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH v4 net-next 10/15] net: dsa: Validate hardware support for MST
Date: Wed, 16 Mar 2022 15:03:49 +0200 [thread overview]
Message-ID: <20220316130349.kmjonrhsx7upj55h@skbuf> (raw)
In-Reply-To: <8735jil0m1.fsf@waldekranz.com>
On Wed, Mar 16, 2022 at 10:15:18AM +0100, Tobias Waldekranz wrote:
> >> +int dsa_port_mst_enable(struct dsa_port *dp, bool on,
> >> + struct netlink_ext_ack *extack)
> >> +{
> >> + if (!on)
> >> + return 0;
> >> +
> >> + if (!dsa_port_supports_mst(dp)) {
> >> + NL_SET_ERR_MSG_MOD(extack, "Hardware does not support MST");
> >> + return -EINVAL;
> >> + }
> >> +
> >> + return 0;
> >> +}
> >
> > Experimenting a bit... maybe this looks tidier? We make the "if" condition
> > have the same basic structure as the previous "if (br_mst_enabled(br) &&
> > !dsa_port_supports_mst(dp))", albeit transformed using De Morgan's rules.
> >
> > {
> > if (!on || dsa_port_supports_mst(dp))
> > return 0;
> >
> > NL_SET_ERR_MSG_MOD(extack, "Hardware does not support MST");
> > return -EINVAL;
> > }
>
> I initially had it like this. It looks tidier, yes - but to me the
> intent is less obvious when reading it. How about:
>
> {
> if (on && !dsa_port_supports_mst(dp)) {
> NL_SET_ERR_MSG_MOD(extack, "Hardware does not support MST");
> return -EINVAL;
> }
>
> return 0;
> }
Yes, let's go with this.
next prev parent reply other threads:[~2022-03-16 13:03 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 0:25 [Bridge] [PATCH v4 net-next 00/15] net: bridge: Multiple Spanning Trees Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 01/15] net: bridge: mst: Multiple Spanning Tree (MST) mode Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 02/15] net: bridge: mst: Allow changing a VLAN's MSTI Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 03/15] net: bridge: mst: Support setting and reporting MST port states Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 9:52 ` [Bridge] " Nikolay Aleksandrov
2022-03-15 9:52 ` Nikolay Aleksandrov
2022-03-15 16:54 ` [Bridge] " Vladimir Oltean
2022-03-15 16:54 ` Vladimir Oltean
2022-03-15 22:35 ` [Bridge] " Tobias Waldekranz
2022-03-15 22:35 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 04/15] net: bridge: mst: Notify switchdev drivers of MST mode changes Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 5:32 ` [Bridge] " Jakub Kicinski
2022-03-15 5:32 ` Jakub Kicinski
2022-03-15 22:28 ` [Bridge] " Tobias Waldekranz
2022-03-15 22:28 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 05/15] net: bridge: mst: Notify switchdev drivers of VLAN MSTI migrations Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 06/15] net: bridge: mst: Notify switchdev drivers of MST state changes Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 07/15] net: bridge: mst: Add helper to map an MSTI to a VID set Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 08/15] net: bridge: mst: Add helper to check if MST is enabled Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 09/15] net: dsa: Never offload FDB entries on standalone ports Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 16:33 ` [Bridge] " Vladimir Oltean
2022-03-15 16:33 ` Vladimir Oltean
2022-03-15 22:26 ` [Bridge] " Tobias Waldekranz
2022-03-15 22:26 ` Tobias Waldekranz
2022-03-15 22:42 ` [Bridge] " Vladimir Oltean
2022-03-15 22:42 ` Vladimir Oltean
2022-03-15 22:57 ` [Bridge] " Tobias Waldekranz
2022-03-15 22:57 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 10/15] net: dsa: Validate hardware support for MST Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 17:11 ` [Bridge] " Vladimir Oltean
2022-03-15 17:11 ` Vladimir Oltean
2022-03-16 9:15 ` [Bridge] " Tobias Waldekranz
2022-03-16 9:15 ` Tobias Waldekranz
2022-03-16 13:03 ` Vladimir Oltean [this message]
2022-03-16 13:03 ` Vladimir Oltean
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 11/15] net: dsa: Pass VLAN MSTI migration notifications to driver Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 12/15] net: dsa: Handle MST state changes Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 16:42 ` [Bridge] " Vladimir Oltean
2022-03-15 16:42 ` Vladimir Oltean
2022-03-15 16:44 ` [Bridge] " Vladimir Oltean
2022-03-15 16:44 ` Vladimir Oltean
2022-03-16 9:45 ` [Bridge] " Tobias Waldekranz
2022-03-16 9:45 ` Tobias Waldekranz
2022-03-16 9:51 ` [Bridge] " Tobias Waldekranz
2022-03-16 9:51 ` Tobias Waldekranz
2022-03-16 13:02 ` [Bridge] " Vladimir Oltean
2022-03-16 13:02 ` Vladimir Oltean
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 13/15] net: dsa: mv88e6xxx: Disentangle STU from VTU Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 14/15] net: dsa: mv88e6xxx: Export STU as devlink region Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
2022-03-15 0:25 ` [Bridge] [PATCH v4 net-next 15/15] net: dsa: mv88e6xxx: MST Offloading Tobias Waldekranz
2022-03-15 0:25 ` Tobias Waldekranz
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=20220316130349.kmjonrhsx7upj55h@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=idosch@nvidia.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matt@codeconstruct.com.au \
--cc=me@cooperlees.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@gmail.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.