BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hengqi Chen <hengqi.chen@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, olsajiri@gmail.com, acme@redhat.com
Subject: Re: [PATCH bpf-next v2] libbpf: Allow Golang symbols in uprobe secdef
Date: Fri, 29 Sep 2023 22:50:24 +0000	[thread overview]
Message-ID: <169602782436.32717.11851217001971719983.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230929155954.92448-1-hengqi.chen@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Fri, 29 Sep 2023 15:59:54 +0000 you wrote:
> Golang symbols in ELF files are different from C/C++
> which contains special characters like '*', '(' and ')'.
> With generics, things get more complicated, there are
> symbols like:
> 
>   github.com/cilium/ebpf/internal.(*Deque[go.shape.interface { Format(fm
>   t.State, int32); TypeName() string;github.com/cilium/ebpf/btf.copy() g
>   ithub.com/cilium/ebpf/btf.Type}]).Grow
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] libbpf: Allow Golang symbols in uprobe secdef
    https://git.kernel.org/bpf/bpf-next/c/2147c8d07e1a

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



      reply	other threads:[~2023-09-29 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 15:59 [PATCH bpf-next v2] libbpf: Allow Golang symbols in uprobe secdef Hengqi Chen
2023-09-29 22: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=169602782436.32717.11851217001971719983.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=acme@redhat.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=hengqi.chen@gmail.com \
    --cc=olsajiri@gmail.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