All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, alexei.starovoitov@gmail.com,
	andrii@kernel.org, daniel@iogearbox.net,
	mykyta.yatsenko5@gmail.com, toke@redhat.com,
	kernel-team@meta.com
Subject: Re: [PATCH bpf-next v1 1/1] selftests/bpf: Copy test_kmods when installing selftest
Date: Wed, 13 Aug 2025 23:10:06 +0000	[thread overview]
Message-ID: <175512660610.3810269.2938068331915732327.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250812175039.2323570-1-ameryhung@gmail.com>

Hello:

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

On Tue, 12 Aug 2025 10:50:39 -0700 you wrote:
> Commit d6212d82bf26 ("selftests/bpf: Consolidate kernel modules into
> common directory") consolidated the Makefile of test_kmods. However,
> since it removed test_kmods from TEST_GEN_PROGS_EXTENDED, the kernel
> modules required by bpf selftests are now missing from kselftest_install
> when "make install". Fix it by adding test_kmod to TEST_GEN_FILES.
> 
> Fixes: d6212d82bf26 ("selftests/bpf: Consolidate kernel modules into common directory")
> Signed-off-by: Amery Hung <ameryhung@gmail.com>
> 
> [...]

Here is the summary with links:
  - [bpf-next,v1,1/1] selftests/bpf: Copy test_kmods when installing selftest
    https://git.kernel.org/bpf/bpf-next/c/07866544e410

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



      reply	other threads:[~2025-08-13 23:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12 17:50 [PATCH bpf-next v1 1/1] selftests/bpf: Copy test_kmods when installing selftest Amery Hung
2025-08-13 23: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=175512660610.3810269.2938068331915732327.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=toke@redhat.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.