From: Larysa Zaremba <larysa.zaremba@intel.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH net-next v2] net: lan966x: Use automatic selection of VCAP rule actionset
Date: Thu, 16 Feb 2023 14:54:05 +0100 [thread overview]
Message-ID: <Y+41fTUfz8Kx6ujH@lincoln> (raw)
In-Reply-To: <20230216122907.2207291-1-horatiu.vultur@microchip.com>
On Thu, Feb 16, 2023 at 01:29:07PM +0100, Horatiu Vultur wrote:
> Since commit 81e164c4aec5 ("net: microchip: sparx5: Add automatic
> selection of VCAP rule actionset") the VCAP API has the capability to
> select automatically the actionset based on the actions that are attached
> to the rule. So it is not needed anymore to hardcore the actionset in the
I am sure, you've meant 'hardcode'
> driver, therefore it is OK to remove this.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> v1->v2:
> - improve the commit message by mentioning the commit which allows
> to make this change
> ---
> drivers/net/ethernet/microchip/lan966x/lan966x_tc_flower.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/microchip/lan966x/lan966x_tc_flower.c b/drivers/net/ethernet/microchip/lan966x/lan966x_tc_flower.c
> index bd10a71897418..f960727ecaeec 100644
> --- a/drivers/net/ethernet/microchip/lan966x/lan966x_tc_flower.c
> +++ b/drivers/net/ethernet/microchip/lan966x/lan966x_tc_flower.c
> @@ -261,8 +261,6 @@ static int lan966x_tc_flower_add(struct lan966x_port *port,
> 0);
> err |= vcap_rule_add_action_u32(vrule, VCAP_AF_MASK_MODE,
> LAN966X_PMM_REPLACE);
> - err |= vcap_set_rule_set_actionset(vrule,
> - VCAP_AFS_BASE_TYPE);
Is this the only location, where this can be done? I'm not very familiar with
this driver, would it maybe make sense to check out lan966x_ptp_add_trap() too?
> if (err)
> goto out;
>
> --
> 2.38.0
>
next prev parent reply other threads:[~2023-02-16 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 12:29 [PATCH net-next v2] net: lan966x: Use automatic selection of VCAP rule actionset Horatiu Vultur
2023-02-16 13:54 ` Larysa Zaremba [this message]
2023-02-17 8:08 ` Horatiu Vultur
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=Y+41fTUfz8Kx6ujH@lincoln \
--to=larysa.zaremba@intel.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).