public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
	yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
	sdf@google.com, haoluo@google.com
Subject: Re: [PATCHv4 bpf-next 0/3] selftests/bpf: Add read_build_id function
Date: Fri, 31 Mar 2023 16:50:19 +0000	[thread overview]
Message-ID: <168028141949.20294.2685025381154219952.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230331093157.1749137-1-jolsa@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 31 Mar 2023 11:31:54 +0200 you wrote:
> hi,
> this selftests cleanup was previously posted as part of file build id changes [1],
> which might take more time, so I'm sending the selftests changes separately so it
> won't get stuck.
> 
> v4 changes:
>   - added size argument to read_build_id [Andrii]
>   - condition changes in parse_build_id_buf [Andrii]
>   - use ELF_C_READ_MMAP in elf_begin [Andrii]
>   - return -ENOENT in read_build_id if build id is not found [Andrii]
>   - dropped elf class check [Andrii]
> 
> [...]

Here is the summary with links:
  - [PATCHv4,bpf-next,1/3] selftests/bpf: Add err.h header
    https://git.kernel.org/bpf/bpf-next/c/328bafc9a373
  - [PATCHv4,bpf-next,2/3] selftests/bpf: Add read_build_id function
    https://git.kernel.org/bpf/bpf-next/c/88dc8b3605b3
  - [PATCHv4,bpf-next,3/3] selftests/bpf: Replace extract_build_id with read_build_id
    https://git.kernel.org/bpf/bpf-next/c/dcc46f51d770

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



      parent reply	other threads:[~2023-03-31 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  9:31 [PATCHv4 bpf-next 0/3] selftests/bpf: Add read_build_id function Jiri Olsa
2023-03-31  9:31 ` [PATCHv4 bpf-next 1/3] selftests/bpf: Add err.h header Jiri Olsa
2023-03-31  9:31 ` [PATCHv4 bpf-next 2/3] selftests/bpf: Add read_build_id function Jiri Olsa
2023-03-31  9:31 ` [PATCHv4 bpf-next 3/3] selftests/bpf: Replace extract_build_id with read_build_id Jiri Olsa
2023-03-31 16:50 ` 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=168028141949.20294.2685025381154219952.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=sdf@google.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