From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, kernel-team@fb.com, bruce.w.allan@intel.com,
jeyu@kernel.org, gregkh@linuxfoundation.org,
yamada.masahiro@socionext.com
Subject: Re: [PATCH RESEND bpf-next 1/2] kbuild: skip module BTF generation for out-of-tree external modules
Date: Wed, 25 Nov 2020 00:50:05 +0000 [thread overview]
Message-ID: <160626540526.31715.17769039124481474588.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201121070829.2612884-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 20 Nov 2020 23:08:28 -0800 you wrote:
> In some modes of operation, Kbuild allows to build modules without having
> vmlinux image around. In such case, generation of module BTF is impossible.
> This patch changes the behavior to emit a warning about impossibility of
> generating kernel module BTF, instead of breaking the build. This is especially
> important for out-of-tree external module builds.
>
> In vmlinux-less mode:
>
> [...]
Here is the summary with links:
- [RESEND,bpf-next,1/2] kbuild: skip module BTF generation for out-of-tree external modules
https://git.kernel.org/bpf/bpf-next/c/e732b538f455
- [RESEND,bpf-next,2/2] bpf: sanitize BTF data pointer after module is loaded
https://git.kernel.org/bpf/bpf-next/c/607c543f939d
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:[~2020-11-25 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 7:08 [PATCH RESEND bpf-next 1/2] kbuild: skip module BTF generation for out-of-tree external modules Andrii Nakryiko
2020-11-21 7:08 ` [PATCH RESEND bpf-next 2/2] bpf: sanitize BTF data pointer after module is loaded Andrii Nakryiko
2020-11-25 0:50 ` 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=160626540526.31715.17769039124481474588.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=bruce.w.allan@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeyu@kernel.org \
--cc=kernel-team@fb.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).