Received-SPF: pass (google.com: domain of linux-kernel+bounces-146929-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Subject: Re: [PATCH net-next] sfc: use flow_rule_no_unsupp_control_flags()
To: =?UTF-8?Q?Asbj=c3=b8rn_Sloth_T=c3=b8nnesen?= <ast@fiberby.net>,
 netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
 Eric Dumazet <edumazet@google.com>, Jakub Kicinski <kuba@kernel.org>,
 Paolo Abeni <pabeni@redhat.com>, Martin Habets <habetsm.xilinx@gmail.com>,
 linux-net-drivers@amd.com
References: <20240416134432.9527-1-ast@fiberby.net>
From: Edward Cree <ecree.xilinx@gmail.com>
Message-ID: <496dba36-1d40-e7d1-1250-a350bc590902@gmail.com>
Date: Tue, 16 Apr 2024 14:57:29 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <20240416134432.9527-1-ast@fiberby.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 8bit

On 16/04/2024 14:44, Asbjørn Sloth Tønnesen wrote:
> Adopt nfp-style *_FLOWER_SUPPORTED_CTLFLAGS define.
> 
> Change the check for unsupported control flags, to use the new helper
> flow_rule_is_supp_control_flags().
> 
> Since the helper was based on sfc, then nothing really changes.
> 
> Compile-tested, and compiled objects are identical.
> 
> Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>

Subject line doesn't match the patch (I guess because the helper
 got renamed).

> ---
>  drivers/net/ethernet/sfc/tc.c | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/ethernet/sfc/tc.c b/drivers/net/ethernet/sfc/tc.c
> index 82e8891a619a..5f73f1dea524 100644
> --- a/drivers/net/ethernet/sfc/tc.c
> +++ b/drivers/net/ethernet/sfc/tc.c
> @@ -21,6 +21,10 @@
>  #include "ef100_rep.h"
>  #include "efx.h"
>  
> +#define SFC_FLOWER_SUPPORTED_CTLFLAGS \
> +	(FLOW_DIS_IS_FRAGMENT | \
> +	 FLOW_DIS_FIRST_FRAG)

I'd rather keep the flags in-line, next to where they're actually
 used.  I.e. we have
    if (flags & FRAGMENT)
        blah;
    if (flags & FIRST_FRAG)
        foo;
    if (!blah_supported(FRAGMENT | FIRST_FRAG))
        return -EEK;
 and it's very clear that anyone changing one of those parts also
 needs to change the other.  Whereas with your #define it's not
 immediately obvious to someone reading the code where that set
 of supported flags comes from conceptually.

-ed