From: Quentin Monnet <quentin@isovalent.com>
To: Gianmarco Lusvardi <glusvardi@posteo.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Corrected GPL license name
Date: Wed, 14 Feb 2024 15:14:46 +0000 [thread overview]
Message-ID: <5bb799e2-492b-49f2-b5f5-7e8f113bf56f@isovalent.com> (raw)
In-Reply-To: <20240213230544.930018-3-glusvardi@posteo.net>
2024-02-13 23:07 UTC+0000 ~ Gianmarco Lusvardi <glusvardi@posteo.net>
> The bpf_doc script refers to the GPL as the "GNU Privacy License".
> I strongly suspect that the author wanted to refer to the GNU General
> Public License, under which the Linux kernel is released, as, to the
> best of my knowledge, there is no license named "GNU Privacy License".
>
> This patch corrects the license name in the script accordingly.
>
> Signed-off-by: Gianmarco Lusvardi <glusvardi@posteo.net>
> ---
> scripts/bpf_doc.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/bpf_doc.py b/scripts/bpf_doc.py
> index 61b7dddedc46..0669bac5e900 100755
> --- a/scripts/bpf_doc.py
> +++ b/scripts/bpf_doc.py
> @@ -513,7 +513,7 @@ eBPF programs can have an associated license, passed along with the bytecode
> instructions to the kernel when the programs are loaded. The format for that
> string is identical to the one in use for kernel modules (Dual licenses, such
> as "Dual BSD/GPL", may be used). Some helper functions are only accessible to
> -programs that are compatible with the GNU Privacy License (GPL).
> +programs that are compatible with the GNU General Public License (GNU GPL).
>
> In order to use such helpers, the eBPF program must be loaded with the correct
> license string passed (via **attr**) to the **bpf**\\ () system call, and this
Not sure how I came up with that one. Thanks for the fix!
Fixes: 56a092c89505 ("bpf: add script and prepare bpf.h for new helpers documentation")
Reviewed-by: Quentin Monnet <quentin@isovalent.com>
next prev parent reply other threads:[~2024-02-14 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 23:05 [PATCH] Corrected GPL license name Gianmarco Lusvardi
2024-02-14 15:14 ` Quentin Monnet [this message]
2024-02-14 16:20 ` 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=5bb799e2-492b-49f2-b5f5-7e8f113bf56f@isovalent.com \
--to=quentin@isovalent.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=glusvardi@posteo.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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).