From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andriin@fb.com,
nathan@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@chromium.org,
masahiroy@kernel.org, michal.lkml@markovi.net,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH bpf-next] kbuild: Do not clean resolve_btfids if the output does not exist
Date: Thu, 11 Feb 2021 19:30:06 +0000 [thread overview]
Message-ID: <161307180674.24457.7910798840196422022.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210211124004.1144344-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Thu, 11 Feb 2021 13:40:04 +0100 you wrote:
> Nathan reported issue with cleaning empty build directory:
>
> $ make -s O=build distclean
> ../../scripts/Makefile.include:4: *** \
> O=/ho...build/tools/bpf/resolve_btfids does not exist. Stop.
>
> The problem that tools scripts require existing output
> directory, otherwise it fails.
>
> [...]
Here is the summary with links:
- [bpf-next] kbuild: Do not clean resolve_btfids if the output does not exist
https://git.kernel.org/bpf/bpf-next/c/0e1aa629f1ce
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-02-11 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 12:40 [PATCH bpf-next] kbuild: Do not clean resolve_btfids if the output does not exist Jiri Olsa
2021-02-11 19:30 ` 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=161307180674.24457.7910798840196422022.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--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