BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 0/2] bpf: Follow up on gen_epilogue
Date: Wed, 04 Sep 2024 19:50:33 +0000	[thread overview]
Message-ID: <172547943352.1148997.10438402101724044034.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240904180847.56947-1-martin.lau@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed,  4 Sep 2024 11:08:43 -0700 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
> 
> The set addresses some follow ups on the earlier gen_epilogue
> patch set.
> 
> Martin KaFai Lau (2):
>   bpf: Remove the insn_buf array stack usage from the inline_bpf_loop()
>   bpf: Fix indentation issue in epilogue_idx
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] bpf: Remove the insn_buf array stack usage from the inline_bpf_loop()
    https://git.kernel.org/bpf/bpf-next/c/940ce73bdec5
  - [bpf-next,2/2] bpf: Fix indentation issue in epilogue_idx
    https://git.kernel.org/bpf/bpf-next/c/00750788dfc6

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



      parent reply	other threads:[~2024-09-04 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 18:08 [PATCH bpf-next 0/2] bpf: Follow up on gen_epilogue Martin KaFai Lau
2024-09-04 18:08 ` [PATCH bpf-next 1/2] bpf: Remove the insn_buf array stack usage from the inline_bpf_loop() Martin KaFai Lau
2024-09-04 18:08 ` [PATCH bpf-next 2/2] bpf: Fix indentation issue in epilogue_idx Martin KaFai Lau
2024-09-04 19:06 ` [PATCH bpf-next 0/2] bpf: Follow up on gen_epilogue Eduard Zingerman
2024-09-04 19: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=172547943352.1148997.10438402101724044034.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@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