BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Luca Boccassi <luca.boccassi@gmail.com>
Cc: bpf@vger.kernel.org, bjorn.topel@intel.com, jackmanb@google.com,
	jiong.wang@netronome.com, jakub.kicinski@netronome.com,
	ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
	john.fastabend@gmail.com, kpsingh@kernel.org, daniel@zonque.org,
	fengc@google.com, joe@ovn.org, jbacik@fb.com, bluca@debian.org
Subject: Re: [PATCH] samples/bpf: relicense bpf_insn.h as GPL-2.0-only OR BSD-2-Clause
Date: Wed, 29 Sep 2021 16:10:06 +0000	[thread overview]
Message-ID: <163293180662.13147.6555296992871982703.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210923000540.47344-1-luca.boccassi@gmail.com>

Hello:

This patch was applied to bpf/bpf.git (refs/heads/master):

On Thu, 23 Sep 2021 01:05:40 +0100 you wrote:
> From: Luca Boccassi <bluca@debian.org>
> 
> libbpf and bpftool have been dual-licensed to facilitate inclusion in
> software that is not compatible with GPL2-only (ie: Apache2), but the
> samples are still GPL2-only.
> 
> Given these files are samples, they get naturally copied around. For example
> it is the case for samples/bpf/bpf_insn.h which was copied into the systemd
> tree: https://github.com/systemd/systemd/blob/main/src/shared/linux/bpf_insn.h
> 
> [...]

Here is the summary with links:
  - samples/bpf: relicense bpf_insn.h as GPL-2.0-only OR BSD-2-Clause
    https://git.kernel.org/bpf/bpf/c/d75fe9cb1dd0

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-09-29 16:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  0:05 [PATCH] samples/bpf: relicense bpf_insn.h as GPL-2.0-only OR BSD-2-Clause luca.boccassi
2021-09-23 10:41 ` Luca Boccassi
2021-09-23 13:42   ` Quentin Monnet
2021-09-23 14:10     ` Simon Horman
2021-09-27 14:07   ` Luca Boccassi
2021-09-27 14:11     ` Daniel Mack
2021-09-27 14:27 ` Luca Boccassi
2021-09-27 14:39   ` Josef Bacik
2021-09-28 15:44 ` Luca Boccassi
2021-09-29 11:01   ` Björn Töpel
2021-09-29 11:05     ` Luca Boccassi
2021-09-29 11:26       ` Magnus Karlsson
2021-09-29 11:27         ` Luca Boccassi
     [not found] ` <CA+i-1C3sjrwtskbSZzera7ANL8dTiVWMBwLRhe=+1Ft6NgfL=A@mail.gmail.com>
2021-09-28 19:09   ` Joe Stringer
     [not found]     ` <CAMOXUJ=gLLCDv0ZuEz77Qvepx9r0uTfy3J3phWuGPMQXsM1FGA@mail.gmail.com>
2021-09-28 19:12       ` Chenbo Feng
2021-09-29 16:06 ` Luca Boccassi
2021-09-29 16:10   ` Daniel Borkmann
2021-09-29 16:37     ` Luca Boccassi
2021-09-29 16:10 ` patchwork-bot+netdevbpf [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=163293180662.13147.6555296992871982703.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bjorn.topel@intel.com \
    --cc=bluca@debian.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=daniel@zonque.org \
    --cc=fengc@google.com \
    --cc=jackmanb@google.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jbacik@fb.com \
    --cc=jiong.wang@netronome.com \
    --cc=joe@ovn.org \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=luca.boccassi@gmail.com \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    /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