All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jose E. Marchesi <jose.marchesi@oracle.com>
Cc: bpf@vger.kernel.org, andrii.nakryiko@gmail.com, yhs@meta.com,
	eddyz87@gmail.com, david.faust@oracle.com,
	cupertino.miranda@oracle.com
Subject: Re: [PATCH bpf-next V2] bpf_helpers.h: define bpf_tail_call_static when building with GCC
Date: Fri, 26 Apr 2024 15:20:27 +0000	[thread overview]
Message-ID: <171414482723.31416.4816635428805026983.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240426145158.14409-1-jose.marchesi@oracle.com>

Hello:

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

On Fri, 26 Apr 2024 16:51:58 +0200 you wrote:
> [Changes from V1;
> - Add minimum GCC version that supports bpf_tail_call_static.]
> 
> The definition of bpf_tail_call_static in tools/lib/bpf/bpf_helpers.h
> is guarded by a preprocessor check to assure that clang is recent
> enough to support it.  This patch updates the guard so the function is
> compiled when using GCC 13 or later as well.
> 
> [...]

Here is the summary with links:
  - [bpf-next,V2] bpf_helpers.h: define bpf_tail_call_static when building with GCC
    https://git.kernel.org/bpf/bpf-next/c/6e25bcf06af0

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



      reply	other threads:[~2024-04-26 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26 14:51 [PATCH bpf-next V2] bpf_helpers.h: define bpf_tail_call_static when building with GCC Jose E. Marchesi
2024-04-26 15:20 ` 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=171414482723.31416.4816635428805026983.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=cupertino.miranda@oracle.com \
    --cc=david.faust@oracle.com \
    --cc=eddyz87@gmail.com \
    --cc=jose.marchesi@oracle.com \
    --cc=yhs@meta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.