All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: davem@davemloft.net, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/7] bpf: drop libbpf from bpf preload.
Date: Tue, 01 Feb 2022 23:00:11 +0000	[thread overview]
Message-ID: <164375641130.5554.16675850401091381766.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220131220528.98088-1-alexei.starovoitov@gmail.com>

Hello:

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

On Mon, 31 Jan 2022 14:05:21 -0800 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
> 
> CO-RE in the kernel support allows bpf preload to switch to light skeleton
> and remove libbpf dependency.
> This reduces the size of bpf_preload_umd from 300kbyte to 19kbyte and
> eventually will make "kernel skeleton" possible.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/7] libbpf: Add support for bpf iter in light skeleton.
    https://git.kernel.org/bpf/bpf-next/c/42d1d53fedc9
  - [bpf-next,2/7] libbpf: Open code low level bpf commands.
    https://git.kernel.org/bpf/bpf-next/c/e981f41fd029
  - [bpf-next,3/7] libbpf: Open code raw_tp_open and link_create commands.
    https://git.kernel.org/bpf/bpf-next/c/c69f94a33d12
  - [bpf-next,4/7] bpf: Remove unnecessary setrlimit from bpf preload.
    https://git.kernel.org/bpf/bpf-next/c/1ddbddd70651
  - [bpf-next,5/7] bpf: Convert bpf preload to light skeleton.
    https://git.kernel.org/bpf/bpf-next/c/79b203926d18
  - [bpf-next,6/7] bpf: Open code obj_get_info_by_fd in bpf preload.
    https://git.kernel.org/bpf/bpf-next/c/18ef5dac934a
  - [bpf-next,7/7] bpf: Drop libbpf, libelf, libz dependency from bpf preload.
    https://git.kernel.org/bpf/bpf-next/c/e96f2d64c812

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-01 23:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 22:05 [PATCH bpf-next 0/7] bpf: drop libbpf from bpf preload Alexei Starovoitov
2022-01-31 22:05 ` [PATCH bpf-next 1/7] libbpf: Add support for bpf iter in light skeleton Alexei Starovoitov
2022-02-01 18:40   ` Martin KaFai Lau
2022-01-31 22:05 ` [PATCH bpf-next 2/7] libbpf: Open code low level bpf commands Alexei Starovoitov
2022-02-01 18:52   ` Martin KaFai Lau
2022-01-31 22:05 ` [PATCH bpf-next 3/7] libbpf: Open code raw_tp_open and link_create commands Alexei Starovoitov
2022-02-01 19:07   ` Martin KaFai Lau
2022-01-31 22:05 ` [PATCH bpf-next 4/7] bpf: Remove unnecessary setrlimit from bpf preload Alexei Starovoitov
2022-02-01 19:09   ` Martin KaFai Lau
2022-01-31 22:05 ` [PATCH bpf-next 5/7] bpf: Convert bpf preload to light skeleton Alexei Starovoitov
2022-02-01 19:18   ` Martin KaFai Lau
2022-01-31 22:05 ` [PATCH bpf-next 6/7] bpf: Open code obj_get_info_by_fd in bpf preload Alexei Starovoitov
2022-02-01 19:26   ` Martin KaFai Lau
2022-01-31 22:05 ` [PATCH bpf-next 7/7] bpf: Drop libbpf, libelf, libz dependency from " Alexei Starovoitov
2022-02-01 19:27   ` Martin KaFai Lau
2022-02-01 23:00 ` 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=164375641130.5554.16675850401091381766.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.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.