From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH iproute2] include: dual license the bpf helper includes
Date: Fri, 21 Jul 2023 19:41:20 -0700 [thread overview]
Message-ID: <20230722024120.6036-1-stephen@networkplumber.org> (raw)
The files bpf_api.h and bpf_elf.h are useful for TC BPF programs
to use. And there is no requirement that those be GPL only;
we intend to allow BSD licensed BPF helpers as well.
This makes the file license same as libbpf.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
include/bpf_api.h | 2 +-
include/bpf_elf.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/bpf_api.h b/include/bpf_api.h
index 82c47089f614..5887d3a851cf 100644
--- a/include/bpf_api.h
+++ b/include/bpf_api.h
@@ -1,4 +1,4 @@
-/* SPDX-License-Identifier: GPL-2.0 */
+/* SPDX-License-Identifier: GPL-2.0 or BSD-3-Clause */
#ifndef __BPF_API__
#define __BPF_API__
diff --git a/include/bpf_elf.h b/include/bpf_elf.h
index 84e8ae00834c..ea8a11c95c0f 100644
--- a/include/bpf_elf.h
+++ b/include/bpf_elf.h
@@ -1,4 +1,4 @@
-/* SPDX-License-Identifier: GPL-2.0 */
+/* SPDX-License-Identifier: GPL-2.0 or BSD-3-Clause */
#ifndef __BPF_ELF__
#define __BPF_ELF__
--
2.39.2
next reply other threads:[~2023-07-22 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 2:41 Stephen Hemminger [this message]
2023-07-22 11:57 ` [PATCH iproute2] include: dual license the bpf helper includes Daniel Borkmann
2023-07-22 16:40 ` 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=20230722024120.6036-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).