netdev - Re: [PATCH bpf-next] bpf: Document BPF licensing.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 16 Sep 2021 13:49:02 -0700
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Daniel Borkmann <daniel@...earbox.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Andrii Nakryiko <andrii@...nel.org>,
        Network Development <netdev@...r.kernel.org>,
        bpf <bpf@...r.kernel.org>, Kernel Team <kernel-team@...com>
Subject: Re: [PATCH bpf-next] bpf: Document BPF licensing.

On Thu, Sep 16, 2021 at 9:05 AM Jonathan Corbet <corbet@....net> wrote:
>
> Alexei Starovoitov <alexei.starovoitov@...il.com> writes:
>
> > From: Alexei Starovoitov <ast@...nel.org>
> >
> > Document and clarify BPF licensing.
>
> Two trivial things that have nothing to do with the actual content...
>
> > Signed-off-by: Alexei Starovoitov <ast@...nel.org>
> > Acked-by: Toke Høiland-Jørgensen <toke@...hat.com>
> > Acked-by: Daniel Borkmann <daniel@...earbox.net>
> > Acked-by: Joe Stringer <joe@...ium.io>
> > Acked-by: Lorenz Bauer <lmb@...udflare.com>
> > Acked-by: Dave Thaler <dthaler@...rosoft.com>
> > ---
> >  Documentation/bpf/bpf_licensing.rst | 91 +++++++++++++++++++++++++++++
> >  1 file changed, 91 insertions(+)
> >  create mode 100644 Documentation/bpf/bpf_licensing.rst
>
> When you add a new file you need to put it into index.rst as well so it
> gets pulled into the docs build.

ok.

> > +under these rules:
> > +https://www.kernel.org/doc/html/latest/process/license-rules.html#id1
>
> I would just write this as Documentation/process/license-rules.rst.  The
> HTML docs build will link it automatically, and readers of the plain-text
> file will know where to go.

Good point. Will fix.