From: patchwork-bot+netdevbpf@kernel.org
To: Alexey Gladkov <legion@kernel.org>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-kbuild@vger.kernel.org, masahiroy@kernel.org,
ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
oleg@redhat.com, alan.maguire@oracle.com
Subject: Re: [PATCH v4] bpf: Remove custom build rule
Date: Fri, 30 Aug 2024 16:00:27 +0000 [thread overview]
Message-ID: <172503362769.2640228.5019658965593399778.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240830074350.211308-1-legion@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 30 Aug 2024 09:43:50 +0200 you wrote:
> According to the documentation, when building a kernel with the C=2
> parameter, all source files should be checked. But this does not happen
> for the kernel/bpf/ directory.
>
> $ touch kernel/bpf/core.o
> $ make C=2 CHECK=true kernel/bpf/core.o
>
> [...]
Here is the summary with links:
- [v4] bpf: Remove custom build rule
https://git.kernel.org/bpf/bpf-next/c/1dd7622ef508
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-08-30 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 15:25 [PATCH v1] bpf: Add missing force_checksrc macro Alexey Gladkov
2024-08-28 16:32 ` Masahiro Yamada
2024-08-28 17:06 ` [PATCH v2] bpf: Remove custom build rule Alexey Gladkov
2024-08-28 17:22 ` Masahiro Yamada
2024-08-28 17:49 ` Alexey Gladkov
2024-08-28 18:10 ` [PATCH v3] " Alexey Gladkov
2024-08-28 18:32 ` Masahiro Yamada
2024-08-28 19:14 ` Oleg Nesterov
2024-08-29 10:12 ` Alan Maguire
2024-08-29 19:24 ` Alexei Starovoitov
2024-08-30 7:43 ` [PATCH v4] " Alexey Gladkov
2024-08-30 16: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=172503362769.2640228.5019658965593399778.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=legion@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=oleg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox