All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neill Kapron <nkapron@google.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
	jolsa@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] libbpf: fix license for btf_relocate.c
Date: Mon, 12 Aug 2024 18:45:40 +0000	[thread overview]
Message-ID: <ZrpYVOaMvEo3UZwf@google.com> (raw)
In-Reply-To: <20240810093504.2111134-1-alan.maguire@oracle.com>

On Sat, Aug 10, 2024 at 10:35:04AM +0100, Alan Maguire wrote:
> License should be
> 
> // SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
> 
> ...as with other libbpf files.
> 
> Fixes: 19e00c897d50 ("libbpf: Split BTF relocation")
> Reported-by: Neill Kapron <nkapron@google.com>
> Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
> ---
>  tools/lib/bpf/btf_relocate.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/lib/bpf/btf_relocate.c b/tools/lib/bpf/btf_relocate.c
> index 17f8b32f94a0..4f7399d85eab 100644
> --- a/tools/lib/bpf/btf_relocate.c
> +++ b/tools/lib/bpf/btf_relocate.c
> @@ -1,4 +1,4 @@
> -// SPDX-License-Identifier: GPL-2.0
> +// SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
>  /* Copyright (c) 2024, Oracle and/or its affiliates. */
>  
>  #ifndef _GNU_SOURCE
> -- 
> 2.43.5
>

Thanks Alan. Patch LGTM, but I'm not certain of the legal aspect of
relicencing, so will leave reviewed-by to others.

Neill

  reply	other threads:[~2024-08-12 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-10  9:35 [PATCH bpf-next] libbpf: fix license for btf_relocate.c Alan Maguire
2024-08-12 18:45 ` Neill Kapron [this message]
2024-08-12 20:57   ` Andrii Nakryiko
2024-08-12 19:19 ` Yonghong Song
2024-08-12 21:00 ` 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=ZrpYVOaMvEo3UZwf@google.com \
    --to=nkapron@google.com \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --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 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.