[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190516152543.729c6cb0@cakuba.netronome.com>
Date: Thu, 16 May 2019 15:25:43 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev@...r.kernel.org, davem@...emloft.net,
xdp-newbies@...r.kernel.org, bpf@...r.kernel.org,
Stephen Hemminger <sthemmin@...rosoft.com>
Subject: Re: [PATCH net 3/3] netdevice: clarify meaning of rx_handler_result
On Thu, 16 May 2019 14:54:23 -0700, Stephen Hemminger wrote:
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index 44b47e9df94a..56f613561909 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -374,10 +374,10 @@ typedef enum gro_result gro_result_t;
>
> /*
> * enum rx_handler_result - Possible return values for rx_handlers.
> - * @RX_HANDLER_CONSUMED: skb was consumed by rx_handler, do not process it
> - * further.
> - * @RX_HANDLER_ANOTHER: Do another round in receive path. This is indicated in
> - * case skb->dev was changed by rx_handler.
> + * @RX_HANDLER_CONSUMED: skb was consumed by rx_handler.
> + * Do not process it further.
> + * @RX_HANDLER_ANOTHER: skb->dev was modified by rx_handler,
> + * Do another round in receive path. This is indicated in
s/ This is indicated in//
> * @RX_HANDLER_EXACT: Force exact delivery, no wildcard.
> * @RX_HANDLER_PASS: Do nothing, pass the skb as if no rx_handler was called.
> *
Powered by blists - more mailing lists