From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@redhat.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
masahiroy@kernel.org, michal.lkml@markovi.net,
ndesaulniers@google.com, lkp@intel.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kbuild@vger.kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@chromium.org
Subject: Re: [PATCHv3 bpf-next] kbuild: Unify options for BTF generation for vmlinux and modules
Date: Tue, 02 Nov 2021 01:20:06 +0000 [thread overview]
Message-ID: <163581600680.29215.13986498417182964591.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211029125729.70002-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 29 Oct 2021 14:57:29 +0200 you wrote:
> Using new PAHOLE_FLAGS variable to pass extra arguments to
> pahole for both vmlinux and modules BTF data generation.
>
> Adding new scripts/pahole-flags.sh script that detect and
> prints pahole options.
>
> [ fixed issues found by kernel test robot ]
> Cc: kernel test robot <lkp@intel.com>
> Acked-by: Andrii Nakryiko <andrii@kernel.org>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
>
> [...]
Here is the summary with links:
- [PATCHv3,bpf-next] kbuild: Unify options for BTF generation for vmlinux and modules
https://git.kernel.org/bpf/bpf-next/c/9741e07ece7c
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:[~2021-11-02 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 12:57 [PATCHv3 bpf-next] kbuild: Unify options for BTF generation for vmlinux and modules Jiri Olsa
2021-11-02 1:20 ` 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=163581600680.29215.13986498417182964591.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=john.fastabend@gmail.com \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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