public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Vernet <void@manifault.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
	yhs@meta.com, john.fastabend@gmail.com, kpsingh@kernel.org,
	sdf@google.com, haoluo@google.com, jolsa@kernel.org,
	linux-kernel@vger.kernel.org, kernel-team@meta.com,
	corbet@lwn.net, hch@infradead.org, acme@kernel.org,
	alan.maguire@oracle.com
Subject: Re: [PATCH bpf-next v3 0/4] bpf: Add __bpf_kfunc tag for kfunc definitions
Date: Wed, 01 Feb 2023 23:30:20 +0000	[thread overview]
Message-ID: <167529422014.24245.9433110504480439659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230201173016.342758-1-void@manifault.com>

Hello:

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

On Wed,  1 Feb 2023 11:30:12 -0600 you wrote:
> This is v3 of the patchset [0]. v2 can be found at [1].
> 
> [0]: https://lore.kernel.org/bpf/Y7kCsjBZ%2FFrsWW%2Fe@maniforge.lan/T/
> [1]: https://lore.kernel.org/lkml/20230123171506.71995-1-void@manifault.com/
> 
> Changelog:
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/4] bpf: Add __bpf_kfunc tag for marking kernel functions as kfuncs
    https://git.kernel.org/bpf/bpf-next/c/57e7c169cd6a
  - [bpf-next,v3,2/4] bpf: Document usage of the new __bpf_kfunc macro
    https://git.kernel.org/bpf/bpf-next/c/98e6ab7a0435
  - [bpf-next,v3,3/4] bpf: Add __bpf_kfunc tag to all kfuncs
    https://git.kernel.org/bpf/bpf-next/c/400031e05adf
  - [bpf-next,v3,4/4] selftests/bpf: Add testcase for static kfunc with unused arg
    https://git.kernel.org/bpf/bpf-next/c/6aed15e330bf

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



      parent reply	other threads:[~2023-02-01 23:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 17:30 [PATCH bpf-next v3 0/4] bpf: Add __bpf_kfunc tag for kfunc definitions David Vernet
2023-02-01 17:30 ` [PATCH bpf-next v3 1/4] bpf: Add __bpf_kfunc tag for marking kernel functions as kfuncs David Vernet
2023-02-01 17:30 ` [PATCH bpf-next v3 2/4] bpf: Document usage of the new __bpf_kfunc macro David Vernet
2023-02-01 17:30 ` [PATCH bpf-next v3 3/4] bpf: Add __bpf_kfunc tag to all kfuncs David Vernet
2023-02-01 17:30 ` [PATCH bpf-next v3 4/4] selftests/bpf: Add testcase for static kfunc with unused arg David Vernet
2023-02-01 23: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=167529422014.24245.9433110504480439659.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=acme@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=hch@infradead.org \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=void@manifault.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox