mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Larysa Zaremba <larysa.zaremba@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
	Mateusz Pacuszka <mateuszx.pacuszka@intel.com>
Subject: Re: [PATCH iwl-next v3 5/6] ice: support egress drop rules on PF
Date: Thu, 13 Feb 2025 23:35:44 +0100	[thread overview]
Message-ID: <Z65zwAq/aJjqDaY1@lzaremba-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <a2828574-8b78-47a8-9ca3-a531f234a4c9@intel.com>

On Wed, Feb 12, 2025 at 01:36:18PM -0800, Tony Nguyen wrote:
> 
> 
> On 2/8/2025 5:22 AM, Larysa Zaremba wrote:
> 
> ...
> 
> > @@ -8393,20 +8395,42 @@ ice_setup_tc_cls_flower(struct ice_netdev_priv *np,
> >   }
> >   /**
> > - * ice_setup_tc_block_cb - callback handler registered for TC block
> > + * ice_setup_tc_block_cb_ingress - callback handler for ingress TC block
> >    * @type: TC SETUP type
> >    * @type_data: TC flower offload data that contains user input
> >    * @cb_priv: netdev private data
> >    */
> >   static int
> > -ice_setup_tc_block_cb(enum tc_setup_type type, void *type_data, void *cb_priv)
> > +ice_setup_tc_block_cb_ingress(enum tc_setup_type type, void *type_data,
> > +			      void *cb_priv)
> 
> Could you fix the kdocs on the ones that you modify? Most of them are
> missing the Return:
> 
> >   {
> >   	struct ice_netdev_priv *np = cb_priv;
> >   	switch (type) {
> >   	case TC_SETUP_CLSFLOWER:
> >   		return ice_setup_tc_cls_flower(np, np->vsi->netdev,
> > -					       type_data);
> > +					       type_data, true);
> > +	default:
> > +		return -EOPNOTSUPP;
> > +	}
> > +}
> > +
> > +/**
> > + * ice_setup_tc_block_cb_egress - callback handler for egress TC block
> > + * @type: TC SETUP type
> > + * @type_data: TC flower offload data that contains user input
> > + * @cb_priv: netdev private data
> > + */
> > +static int
> > +ice_setup_tc_block_cb_egress(enum tc_setup_type type, void *type_data,
> > +			     void *cb_priv)
> 
> And correct the ones that you're adding.
> 
> I believe there's issues of this or the previous in patches 2-5.
> 
> Thanks,
> Tony
>

Fixed in v4. Thanks.

> > +{
> > +	struct ice_netdev_priv *np = cb_priv;
> > +
> > +	switch (type) {
> > +	case TC_SETUP_CLSFLOWER:
> > +		return ice_setup_tc_cls_flower(np, np->vsi->netdev,
> > +					       type_data, false);
> >   	default:
> >   		return -EOPNOTSUPP;
> >   	}
> 

  reply	other threads:[~2025-02-14  9:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08 13:22 [PATCH iwl-next v3 0/6] ice: LLDP support for VFs Larysa Zaremba
2025-02-08 13:22 ` [PATCH iwl-next v3 1/6] ice: fix check for existing switch rule Larysa Zaremba
2025-02-08 13:22 ` [PATCH iwl-next v3 2/6] ice: do not add LLDP-specific filter if not necessary Larysa Zaremba
2025-02-08 13:22 ` [PATCH iwl-next v3 3/6] ice: receive LLDP on trusted VFs Larysa Zaremba
2025-02-08 13:22 ` [PATCH iwl-next v3 4/6] ice: remove headers argument from ice_tc_count_lkups Larysa Zaremba
2025-02-08 13:22 ` [PATCH iwl-next v3 5/6] ice: support egress drop rules on PF Larysa Zaremba
2025-02-12 21:36   ` Tony Nguyen
2025-02-13 22:35     ` Larysa Zaremba [this message]
2025-02-08 13:22 ` [PATCH iwl-next v3 6/6] ice: enable LLDP TX for VFs through tc Larysa Zaremba

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=Z65zwAq/aJjqDaY1@lzaremba-mobl.ger.corp.intel.com \
    --to=larysa.zaremba@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mateuszx.pacuszka@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.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

all inboxes | Powered by JetHome®