Netdev List
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Jian Shen <shenjian15@huawei.com>,
	daniel@iogearbox.net, shmulik@metanetworks.com
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, linuxarm@openeuler.org
Subject: RE: [PATCH net] test_bpf: fix incorrect netdev features
Date: Wed, 22 Jun 2022 18:32:35 -0700	[thread overview]
Message-ID: <62b3c2b310915_6a3b2208bf@john.notmuch> (raw)
In-Reply-To: <20220622135002.8263-1-shenjian15@huawei.com>

Jian Shen wrote:
> The prototype of .features is netdev_features_t, it should use
> NETIF_F_LLTX and NETIF_F_HW_VLAN_STAG_TX, not NETIF_F_LLTX_BIT
> and NETIF_F_HW_VLAN_STAG_TX_BIT.
> 
> Fixes: cf204a718357 ("test_bpf: Introduce 'gso_linear_no_head_frag' skb_segment test")
> 
> Signed-off-by: Jian Shen <shenjian15@huawei.com>
> ---

Acked-by: John Fastabend <john.fastabend@gmail.com>

  reply	other threads:[~2022-06-23  1:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 13:50 [PATCH net] test_bpf: fix incorrect netdev features Jian Shen
2022-06-23  1:32 ` John Fastabend [this message]
2022-06-23  2:30 ` patchwork-bot+netdevbpf

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=62b3c2b310915_6a3b2208bf@john.notmuch \
    --to=john.fastabend@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=linuxarm@openeuler.org \
    --cc=netdev@vger.kernel.org \
    --cc=shenjian15@huawei.com \
    --cc=shmulik@metanetworks.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