BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jinghao Jia <jinghao7@illinois.edu>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
	jolsa@kernel.org, jikos@kernel.org, bentiss@kernel.org,
	masahiroy@kernel.org, n.schier@avm.de, ruqin@redhat.com,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-input@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Makefile fixes for samples/{bpf,hid}
Date: Thu, 06 Feb 2025 01:00:35 +0000	[thread overview]
Message-ID: <173880363576.959069.2235034336278672667.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250203085506.220297-1-jinghao7@illinois.edu>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Mon,  3 Feb 2025 02:55:03 -0600 you wrote:
> Hi everyone,
> 
> Following commit 13b25489b6f8 ("kbuild: change working directory to
> external module directory with M="), the Makefiles for both bpf and hid
> samples are broken due to the use of the relative vmlinux path (i.e.,
> ./vmlinux) when generating vmlinux.h. Additionally, samples/hid experience
> the same problem that was fixed for samples/bpf in commit 5a6ea7022ff4
> ("samples/bpf: Remove unnecessary -I flags from libbpf EXTRA_CFLAGS").
> 
> [...]

Here is the summary with links:
  - [v3,1/3] samples/hid: remove unnecessary -I flags from libbpf EXTRA_CFLAGS
    (no matching commit)
  - [v3,2/3] samples/bpf: fix broken vmlinux path for VMLINUX_BTF
    https://git.kernel.org/bpf/bpf-next/c/94f53edc64e1
  - [v3,3/3] samples/hid: fix broken vmlinux path for VMLINUX_BTF
    (no matching commit)

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



      parent reply	other threads:[~2025-02-06  1:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03  8:55 [PATCH v3 0/3] Makefile fixes for samples/{bpf,hid} Jinghao Jia
2025-02-03  8:55 ` [PATCH v3 1/3] samples/hid: remove unnecessary -I flags from libbpf EXTRA_CFLAGS Jinghao Jia
2025-02-03  8:55 ` [PATCH v3 2/3] samples/bpf: fix broken vmlinux path for VMLINUX_BTF Jinghao Jia
2025-02-06  0:54   ` Andrii Nakryiko
2025-02-03  8:55 ` [PATCH v3 3/3] samples/hid: " Jinghao Jia
2025-02-04 10:09 ` (subset) [PATCH v3 0/3] Makefile fixes for samples/{bpf,hid} Benjamin Tissoires
2025-02-06  1: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=173880363576.959069.2235034336278672667.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=jikos@kernel.org \
    --cc=jinghao7@illinois.edu \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=n.schier@avm.de \
    --cc=ruqin@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --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