From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, daniel@iogearbox.net, ast@kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH bpf-next 2/3] bpf: Sync uapi bpf.h to tools/
Date: Tue, 3 Mar 2020 15:05:02 -0500 [thread overview]
Message-ID: <20200303200503.226217-3-willemdebruijn.kernel@gmail.com> (raw)
In-Reply-To: <20200303200503.226217-1-willemdebruijn.kernel@gmail.com>
From: Willem de Bruijn <willemb@google.com>
sync tools/include/uapi/linux/bpf.h to match include/uapi/linux/bpf.h
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
tools/include/uapi/linux/bpf.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h
index 906e9f2752db..7c689f4552dd 100644
--- a/tools/include/uapi/linux/bpf.h
+++ b/tools/include/uapi/linux/bpf.h
@@ -3176,6 +3176,7 @@ struct __sk_buff {
__u32 wire_len;
__u32 gso_segs;
__bpf_md_ptr(struct bpf_sock *, sk);
+ __u32 gso_size;
};
struct bpf_tunnel_key {
--
2.25.0.265.gbab2e86ba0-goog
next prev parent reply other threads:[~2020-03-03 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 20:05 [PATCH bpf-next 0/3] add gso_size to __sk_buff Willem de Bruijn
2020-03-03 20:05 ` [PATCH bpf-next 1/3] bpf: " Willem de Bruijn
2020-03-03 20:05 ` Willem de Bruijn [this message]
2020-03-03 20:05 ` [PATCH bpf-next 3/3] selftests/bpf: test new __sk_buff field gso_size Willem de Bruijn
2020-03-03 22:56 ` [PATCH bpf-next 0/3] add gso_size to __sk_buff Petar Penkov
2020-03-04 0:31 ` Alexei Starovoitov
-- strict thread matches above, loose matches on Subject: below --
2020-01-21 19:54 [PATCH bpf-next 0/3] bpf: tcp: Add bpf_cubic example Martin KaFai Lau
2020-01-21 19:54 ` [PATCH bpf-next 2/3] bpf: Sync uapi bpf.h to tools/ Martin KaFai Lau
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=20200303200503.226217-3-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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