public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Donglin Peng <dolinux.peng@gmail.com>
Cc: alan.maguire@oracle.com, eddyz87@gmail.com, ast@kernel.org,
	daniel@iogearbox.net, song@kernel.org, andrii@kernel.org,
	haoluo@google.com, yonghong.song@linux.dev, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] libbpf: checking the btf_type kind when fixing variable offsets
Date: Fri, 21 Jun 2024 18:10:33 +0000	[thread overview]
Message-ID: <171899343355.16505.13108622504134914457.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240619122355.426405-1-dolinux.peng@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Wed, 19 Jun 2024 05:23:55 -0700 you wrote:
> I encountered an issue when building the test_progs from the repository[1]:
> 
> $ pwd
> /work/Qemu/x86_64/linux-6.10-rc2/tools/testing/selftests/bpf/
> 
> $ make test_progs V=1
> ...
> ./tools/sbin/bpftool gen object ./ip_check_defrag.bpf.linked2.o ./ip_check_defrag.bpf.linked1.o
> libbpf: failed to find symbol for variable 'bpf_dynptr_slice' in section '.ksyms'
> Error: failed to link './ip_check_defrag.bpf.linked1.o': No such file or directory (2)
> ...
> 
> [...]

Here is the summary with links:
  - [v2] libbpf: checking the btf_type kind when fixing variable offsets
    https://git.kernel.org/bpf/bpf-next/c/cc5083d1f388

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



      reply	other threads:[~2024-06-21 18:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 12:23 [PATCH v2] libbpf: checking the btf_type kind when fixing variable offsets Donglin Peng
2024-06-21 18: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=171899343355.16505.13108622504134914457.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dolinux.peng@gmail.com \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --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