All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>, davem@davemloft.net
Cc: brouer@redhat.com, daniel@iogearbox.net, kuba@kernel.org,
	andrii@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org,
	kernel-team@fb.com
Subject: Re: [PATCH bpf-next] bpf: Document BPF licensing.
Date: Thu, 16 Sep 2021 09:49:10 +0200	[thread overview]
Message-ID: <0d82359a-067b-b590-ae19-d360ccc7c0dd@redhat.com> (raw)
In-Reply-To: <20210916032104.35822-1-alexei.starovoitov@gmail.com>


On 16/09/2021 05.21, Alexei Starovoitov wrote:
> From: Alexei Starovoitov<ast@kernel.org>
>
> Document and clarify BPF licensing.
>
> Signed-off-by: Alexei Starovoitov<ast@kernel.org>
> Acked-by: Toke Høiland-Jørgensen<toke@redhat.com>
> Acked-by: Daniel Borkmann<daniel@iogearbox.net>
> Acked-by: Joe Stringer<joe@cilium.io>
> Acked-by: Lorenz Bauer<lmb@cloudflare.com>
> Acked-by: Dave Thaler<dthaler@microsoft.com>
> ---
>   Documentation/bpf/bpf_licensing.rst | 91 +++++++++++++++++++++++++++++
>   1 file changed, 91 insertions(+)
>   create mode 100644 Documentation/bpf/bpf_licensing.rst


Thanks for working on this, it is good this gets clarified.


Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>


  parent reply	other threads:[~2021-09-16  7:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  3:21 [PATCH bpf-next] bpf: Document BPF licensing Alexei Starovoitov
2021-09-16  5:01 ` Stephen Hemminger
2021-09-16  7:29 ` Simon Horman
2021-09-16  7:49 ` Jesper Dangaard Brouer [this message]
2021-09-16 14:06 ` Jakub Kicinski
2021-09-16 20:04   ` Alexei Starovoitov
2021-09-16 16:05 ` Jonathan Corbet
2021-09-16 20:49   ` Alexei Starovoitov
2021-09-17 16:42     ` KP Singh

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=0d82359a-067b-b590-ae19-d360ccc7c0dd@redhat.com \
    --to=jbrouer@redhat.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kernel-team@fb.com \
    --cc=kuba@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.