Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH 0/2] bpf: Yet another approach to fix the BPF dispatcher thing
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <166760041503.11044.8727035971633367268.git-patchwork-notify@kernel.org>
Date:   Fri, 04 Nov 2022 22:20:15 +0000
References: <20221103120012.717020618@infradead.org>
In-Reply-To: <20221103120012.717020618@infradead.org>
To:     Peter Zijlstra <peterz@infradead.org>
Cc:     olsajiri@gmail.com, ast@kernel.org, daniel@iogearbox.net,
        linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
        bpf@vger.kernel.org, bjorn@kernel.org, toke@redhat.com,
        David.Laight@aculab.com, rostedt@goodmis.org
Precedence: bulk

Hello:

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

On Thu, 03 Nov 2022 13:00:12 +0100 you wrote:
> Hi!
> 
> Even thought the __attribute__((patchable_function_entry())) solution to the
> BPF dispatcher woes works, it turns out to not be supported by the whole range
> of ageing compilers we support. Specifically this attribute seems to be GCC-8
> and later.
> 
> [...]

Here is the summary with links:
  - [1/2] bpf: Revert ("Fix dispatcher patchable function entry to 5 bytes nop")
    (no matching commit)
  - [2/2] bpf: Convert BPF_DISPATCHER to use static_call() (not ftrace)
    https://git.kernel.org/bpf/bpf/c/c86df29d11df

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