From: =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?= <bjorn.topel@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next] i40e: trivial fixup of comments in i40e_xsk.c
Date: Mon, 16 Mar 2020 11:18:49 +0100 [thread overview]
Message-ID: <384f0f02-ad31-979c-5714-dce3f8f6a27a@intel.com> (raw)
In-Reply-To: <158435379870.2479973.8293720099992666964.stgit@carbon>
On 2020-03-16 11:16, Jesper Dangaard Brouer wrote:
> The comment above i40e_run_xdp_zc() was clearly copy-pasted from
> function i40e_xsk_umem_setup, which is just above.
>
> Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
Thanks!
Acked-by: Bj?rn T?pel <bjorn.topel@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e_xsk.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/i40e/i40e_xsk.c b/drivers/net/ethernet/intel/i40e/i40e_xsk.c
> index 0b7d29192b2c..30dfb0d3d185 100644
> --- a/drivers/net/ethernet/intel/i40e/i40e_xsk.c
> +++ b/drivers/net/ethernet/intel/i40e/i40e_xsk.c
> @@ -184,8 +184,6 @@ int i40e_xsk_umem_setup(struct i40e_vsi *vsi, struct xdp_umem *umem,
> * @rx_ring: Rx ring
> * @xdp: xdp_buff used as input to the XDP program
> *
> - * This function enables or disables a UMEM to a certain ring.
> - *
> * Returns any of I40E_XDP_{PASS, CONSUMED, TX, REDIR}
> **/
> static int i40e_run_xdp_zc(struct i40e_ring *rx_ring, struct xdp_buff *xdp)
> @@ -474,7 +472,7 @@ void i40e_zca_free(struct zero_copy_allocator *alloc, unsigned long handle)
> }
>
> /**
> - * i40e_construct_skb_zc - Create skbufff from zero-copy Rx buffer
> + * i40e_construct_skb_zc - Create skbuff from zero-copy Rx buffer
> * @rx_ring: Rx ring
> * @bi: Rx buffer
> * @xdp: xdp_buff
>
>
next prev parent reply other threads:[~2020-03-16 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 10:16 [Intel-wired-lan] [PATCH net-next] i40e: trivial fixup of comments in i40e_xsk.c Jesper Dangaard Brouer
2020-03-16 10:18 ` =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?= [this message]
2020-03-18 17:20 ` Bowers, AndrewX
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=384f0f02-ad31-979c-5714-dce3f8f6a27a@intel.com \
--to=bjorn.topel@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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