From: Alan Maguire <alan.maguire@oracle.com>
To: Neill Kapron <nkapron@google.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, mcgrof@kernel.org, masahiroy@kernel.org,
nathan@kernel.org, mykolal@fb.com, dxu@dxuuu.xyz,
bpf@vger.kernel.org
Subject: Re: [PATCH v6 bpf-next 3/9] libbpf: split BTF relocation
Date: Sat, 10 Aug 2024 10:37:14 +0100 [thread overview]
Message-ID: <cc6b3f06-13d2-481b-b15d-c752c90ff7bc@oracle.com> (raw)
In-Reply-To: <ZraYdV9NjDd0w3oO@google.com>
On 09/08/2024 23:30, Neill Kapron wrote:
> On Thu, Jun 13, 2024 at 10:50:08AM +0100, Alan Maguire wrote:
>
> [...]
>
>> diff --git a/tools/lib/bpf/btf_relocate.c b/tools/lib/bpf/btf_relocate.c
>> new file mode 100644
>> index 000000000000..eabb8755f662
>> --- /dev/null
>> +++ b/tools/lib/bpf/btf_relocate.c
>> @@ -0,0 +1,506 @@
>> +// SPDX-License-Identifier: GPL-2.0
> Did you mean to license this GPL-2.0? [1] states the code should
> licensed BSD-2-Clause OR LGPL-2.1
>
Yeah, aim was simply to be consistent with existing conventions for
libbpf. The only wrinkle with this file is it is included in both kernel
and libbpf, but that is true for relo_core.c too, and that has
// SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
I've sent a fixup patch [1]
Alan
[1]
https://lore.kernel.org/bpf/20240810093504.2111134-1-alan.maguire@oracle.com/
> [...]
>
> [1] https://github.com/libbpf/libbpf?tab=readme-ov-file#license
next prev parent reply other threads:[~2024-08-10 9:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 9:50 [PATCH v6 bpf-next 0/9] bpf: support resilient split BTF Alan Maguire
2024-06-13 9:50 ` [PATCH v6 bpf-next 1/9] libbpf: add btf__distill_base() creating split BTF with distilled base BTF Alan Maguire
2024-06-28 23:30 ` Andrii Nakryiko
2024-06-13 9:50 ` [PATCH v6 bpf-next 2/9] selftests/bpf: test distilled base, split BTF generation Alan Maguire
2024-06-13 9:50 ` [PATCH v6 bpf-next 3/9] libbpf: split BTF relocation Alan Maguire
2024-06-14 0:26 ` Eduard Zingerman
2024-06-17 21:50 ` Andrii Nakryiko
2024-06-18 9:47 ` Alan Maguire
2024-08-09 22:30 ` Neill Kapron
2024-08-10 9:37 ` Alan Maguire [this message]
2024-06-13 9:50 ` [PATCH v6 bpf-next 4/9] selftests/bpf: extend distilled BTF tests to cover " Alan Maguire
2024-06-14 1:13 ` Eduard Zingerman
2024-06-13 9:50 ` [PATCH v6 bpf-next 5/9] libbpf: make btf_parse_elf process .BTF.base transparently Alan Maguire
2024-06-13 9:50 ` [PATCH v6 bpf-next 6/9] resolve_btfids: handle presence of .BTF.base section Alan Maguire
2024-06-14 1:19 ` Eduard Zingerman
2024-06-13 9:50 ` [PATCH v6 bpf-next 7/9] module, bpf: store BTF base pointer in struct module Alan Maguire
2024-06-17 21:50 ` Andrii Nakryiko
2024-06-13 9:50 ` [PATCH v6 bpf-next 8/9] libbpf,bpf: share BTF relocate-related code with kernel Alan Maguire
2024-06-14 22:49 ` Eduard Zingerman
2024-06-17 13:31 ` Alan Maguire
2024-06-17 16:46 ` Eduard Zingerman
2024-06-13 9:50 ` [PATCH v6 bpf-next 9/9] kbuild,bpf: add module-specific pahole flags for distilled base BTF Alan Maguire
2024-06-17 21:50 ` [PATCH v6 bpf-next 0/9] bpf: support resilient split BTF Andrii Nakryiko
2024-06-17 22: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=cc6b3f06-13d2-481b-b15d-c752c90ff7bc@oracle.com \
--to=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--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=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=mykolal@fb.com \
--cc=nathan@kernel.org \
--cc=nkapron@google.com \
--cc=sdf@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox