All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 0/2] Make BPF skeleton easier to use from C++ code
Date: Tue, 15 Feb 2022 18:10:09 +0000	[thread overview]
Message-ID: <164494860982.24331.7075751123876238227.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220212055733.539056-1-andrii@kernel.org>

Hello:

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

On Fri, 11 Feb 2022 21:57:31 -0800 you wrote:
> Add minimal C++-specific additions to BPF skeleton codegen to facilitate
> easier use of C skeletons in C++ applications. These additions don't add any
> extra ongoing maintenance and allows C++ users to fit pure C skeleton better
> into their C++ code base. All that without the need to design, implement and
> support a separate C++ BPF skeleton implementation.
> 
> v1->v2:
>   - use default argument values in T::open() (Alexei).
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,1/2] bpftool: add C++-specific open/load/etc skeleton wrappers
    https://git.kernel.org/bpf/bpf-next/c/bb8ffe61ea45
  - [v2,bpf-next,2/2] selftests/bpf: add Skeleton templated wrapper as an example
    https://git.kernel.org/bpf/bpf-next/c/189e0ecabc17

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



      parent reply	other threads:[~2022-02-15 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12  5:57 [PATCH v2 bpf-next 0/2] Make BPF skeleton easier to use from C++ code Andrii Nakryiko
2022-02-12  5:57 ` [PATCH v2 bpf-next 1/2] bpftool: add C++-specific open/load/etc skeleton wrappers Andrii Nakryiko
2022-02-12  5:57 ` [PATCH v2 bpf-next 2/2] selftests/bpf: add Skeleton templated wrapper as an example Andrii Nakryiko
2022-02-15 18:10 ` 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=164494860982.24331.7075751123876238227.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@fb.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.