From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, akpm@linux-foundation.org,
linux-perf-users@vger.kernel.org, song@kernel.org
Subject: Re: [PATCH bpf-next] MAINTAINERS: record lib/buildid.c as owned by BPF subsystem
Date: Tue, 10 Sep 2024 20:51:59 +0200 [thread overview]
Message-ID: <ZuCVT8EzqZxOxZFx@krava> (raw)
In-Reply-To: <20240909190426.2229940-1-andrii@kernel.org>
On Mon, Sep 09, 2024 at 12:04:26PM -0700, Andrii Nakryiko wrote:
> Build ID fetching code originated from ([0]), and is still both owned
> and heavily relied upon by BPF subsystem.
>
> Fix the original omission in [0] to record this fact in MAINTAINERS.
>
> [0] bd7525dacd7e ("bpf: Move stack_map_get_build_id into lib")
>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f328373463b0..a86834bb4c25 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4098,6 +4098,7 @@ F: include/uapi/linux/btf*
> F: include/uapi/linux/filter.h
> F: kernel/bpf/
> F: kernel/trace/bpf_trace.c
> +F: lib/buildid.c
> F: lib/test_bpf.c
> F: net/bpf/
> F: net/core/filter.c
> @@ -4218,6 +4219,7 @@ L: bpf@vger.kernel.org
> S: Maintained
> F: kernel/bpf/stackmap.c
> F: kernel/trace/bpf_trace.c
> +F: lib/buildid.c
>
> BROADCOM ASP 2.0 ETHERNET DRIVER
> M: Justin Chen <justin.chen@broadcom.com>
> --
> 2.43.5
>
next prev parent reply other threads:[~2024-09-10 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 19:04 [PATCH bpf-next] MAINTAINERS: record lib/buildid.c as owned by BPF subsystem Andrii Nakryiko
2024-09-09 22:24 ` Alexei Starovoitov
2024-09-09 22:38 ` Song Liu
2024-09-10 18:51 ` Jiri Olsa [this message]
2024-09-10 21:40 ` 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=ZuCVT8EzqZxOxZFx@krava \
--to=olsajiri@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-perf-users@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=song@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox