public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Viktor Malik <vmalik@redhat.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
	jolsa@kernel.org, dzickus@redhat.com
Subject: Re: [PATCH bpf-next 0/3] samples/bpf: Allow building as PIE
Date: Thu, 26 Oct 2023 13:40:25 +0000	[thread overview]
Message-ID: <169832762501.4440.5459269955038255670.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1698213811.git.vmalik@redhat.com>

Hello:

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

On Wed, 25 Oct 2023 08:19:11 +0200 you wrote:
> Hi,
> 
> when trying to build samples/bpf as PIE in Fedora, we came across
> several issues, mainly related to the way compiler/linker flags are
> handled in samples/bpf/Makefile. The first 2 commits in this patchset
> address these issues (see commit messages for details).
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/3] samples/bpf: Allow building with custom CFLAGS/LDFLAGS
    https://git.kernel.org/bpf/bpf-next/c/870f09f1ba30
  - [bpf-next,2/3] samples/bpf: Fix passing LDFLAGS to libbpf
    https://git.kernel.org/bpf/bpf-next/c/f56bcfadf7d6
  - [bpf-next,3/3] samples/bpf: Allow building with custom bpftool
    https://git.kernel.org/bpf/bpf-next/c/37db10bc247d

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-10-26 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  6:19 [PATCH bpf-next 0/3] samples/bpf: Allow building as PIE Viktor Malik
2023-10-25  6:19 ` [PATCH bpf-next 1/3] samples/bpf: Allow building with custom CFLAGS/LDFLAGS Viktor Malik
2023-10-25  6:19 ` [PATCH bpf-next 2/3] samples/bpf: Fix passing LDFLAGS to libbpf Viktor Malik
2023-10-25  6:19 ` [PATCH bpf-next 3/3] samples/bpf: Allow building with custom bpftool Viktor Malik
2023-10-26 13:40 ` 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=169832762501.4440.5459269955038255670.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=dzickus@redhat.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=vmalik@redhat.com \
    --cc=yonghong.song@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