All of lore.kernel.org
 help / color / mirror / Atom feed
From: KP Singh <kpsingh@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"David S. Miller" <davem@davemloft.net>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	bpf <bpf@vger.kernel.org>, Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next] bpf: Document BPF licensing.
Date: Fri, 17 Sep 2021 18:42:55 +0200	[thread overview]
Message-ID: <CACYkzJ7HEsFno4fVJ8--An+dPEbqnLY1-y2Px1nFrCyoDGkTJQ@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQ+y5hmCmxM6jKY=TqpM0cGE-uSO=mObZ=LDxiVd9YUzuQ@mail.gmail.com>

On Thu, Sep 16, 2021 at 10:49 PM Alexei Starovoitov
<alexei.starovoitov@gmail.com> wrote:
>
> On Thu, Sep 16, 2021 at 9:05 AM Jonathan Corbet <corbet@lwn.net> wrote:
> >
> > Alexei Starovoitov <alexei.starovoitov@gmail.com> writes:
> >
> > > From: Alexei Starovoitov <ast@kernel.org>
> > >
> > > Document and clarify BPF licensing.
> >
> > Two trivial things that have nothing to do with the actual content...
> >
> > > 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>

Thanks for writing this up!

Acked-by: KP Singh <kpsingh@kernel.org>

      reply	other threads:[~2021-09-17 16:43 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
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 [this message]

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=CACYkzJ7HEsFno4fVJ8--An+dPEbqnLY1-y2Px1nFrCyoDGkTJQ@mail.gmail.com \
    --to=kpsingh@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --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.