public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jonathan Edwards <jonathan.edwards@165gc.onmicrosoft.com>
Cc: andrii.nakryiko@gmail.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] libbpf: add extra BPF_PROG_TYPE check to bpf_object__probe_loading
Date: Mon, 21 Jun 2021 15:30:10 +0000	[thread overview]
Message-ID: <162428941049.14724.10215291624709324980.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210619151007.GA6963@165gc.onmicrosoft.com>

Hello:

This patch was applied to bpf/bpf-next.git (refs/heads/master):

On Sat, 19 Jun 2021 11:10:07 -0400 you wrote:
> eBPF has been backported for RHEL 7 w/ kernel 3.10-940+ [0]. However
> only the following program types are supported [1]
> 
> BPF_PROG_TYPE_KPROBE
> BPF_PROG_TYPE_TRACEPOINT
> BPF_PROG_TYPE_PERF_EVENT
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: add extra BPF_PROG_TYPE check to bpf_object__probe_loading
    https://git.kernel.org/bpf/bpf-next/c/5c10a3dbe922

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



      reply	other threads:[~2021-06-21 15:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 20:22 [PATCH] add multiple program checks to bpf_object__probe_loading Jonathan Edwards
2021-06-17  5:12 ` Andrii Nakryiko
2021-06-18 23:13   ` [PATCH bpf-next] libbpf: add extra BPF_PROG_TYPE check " jjedwa165
2021-06-19  3:26     ` Andrii Nakryiko
2021-06-19 15:10       ` Jonathan Edwards
2021-06-21 15: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=162428941049.14724.10215291624709324980.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=jonathan.edwards@165gc.onmicrosoft.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