netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com, netdev@vger.kernel.org, msuchanek@suse.de,
	jslaby@suse.com, jolsa@redhat.com
Subject: Re: [PATCH bpf] bpf: Limit static tcp-cc functions in the .BTF_ids list to x86
Date: Tue, 11 May 2021 21:30:09 +0000	[thread overview]
Message-ID: <162076860970.722.8375596589065957808.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210508005011.3863757-1-kafai@fb.com>

Hello:

This patch was applied to bpf/bpf.git (refs/heads/master):

On Fri, 7 May 2021 17:50:11 -0700 you wrote:
> During the discussion in [0].  It was pointed out that static functions
> in ppc64 is prefixed with ".".  For example, the 'readelf -s vmlinux.ppc':
> 
> 89326: c000000001383280    24 NOTYPE  LOCAL  DEFAULT   31 cubictcp_init
> 89327: c000000000c97c50   168 FUNC    LOCAL  DEFAULT    2 .cubictcp_init
> 
> The one with FUNC type is ".cubictcp_init" instead of "cubictcp_init".
> The "." seems to be done by arch/powerpc/include/asm/ppc_asm.h.
> 
> [...]

Here is the summary with links:
  - [bpf] bpf: Limit static tcp-cc functions in the .BTF_ids list to x86
    https://git.kernel.org/bpf/bpf/c/569c484f9995

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



      reply	other threads:[~2021-05-11 21:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08  0:50 [PATCH bpf] bpf: Limit static tcp-cc functions in the .BTF_ids list to x86 Martin KaFai Lau
2021-05-11 21:30 ` 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=162076860970.722.8375596589065957808.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jolsa@redhat.com \
    --cc=jslaby@suse.com \
    --cc=kafai@fb.com \
    --cc=kernel-team@fb.com \
    --cc=msuchanek@suse.de \
    --cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).