From: patchwork-bot+netdevbpf@kernel.org
To: Ian Rogers <irogers@google.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, connoro@google.com,
nathan@kernel.org, memxor@gmail.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] tools/resolve_btfids: Install subcmd headers
Date: Wed, 25 Jan 2023 17:30:16 +0000 [thread overview]
Message-ID: <167466781681.13690.9875840754457766562.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230124064324.672022-1-irogers@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 23 Jan 2023 22:43:23 -0800 you wrote:
> Previously tools/lib/subcmd was added to the include path, switch to
> installing the headers and then including from that directory. This
> avoids dependencies on headers internal to tools/lib/subcmd. Add the
> missing subcmd directory to the affected #include.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
>
> [...]
Here is the summary with links:
- [v4,1/2] tools/resolve_btfids: Install subcmd headers
https://git.kernel.org/bpf/bpf-next/c/af03299d8536
- [v4,2/2] tools/resolve_btfids: Alter how HOSTCC is forced
https://git.kernel.org/bpf/bpf-next/c/13e07691a16f
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:[~2023-01-25 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 6:43 [PATCH v4 1/2] tools/resolve_btfids: Install subcmd headers Ian Rogers
2023-01-24 6:43 ` [PATCH v4 2/2] tools/resolve_btfids: Alter how HOSTCC is forced Ian Rogers
2023-01-24 23:08 ` Jiri Olsa
2023-01-31 17:20 ` Nathan Chancellor
2023-01-31 18:08 ` Ian Rogers
2023-01-31 19:25 ` Ian Rogers
2023-01-31 19:33 ` Nathan Chancellor
2023-01-31 20:59 ` Ian Rogers
2023-01-31 21:17 ` Nathan Chancellor
2023-01-31 22:40 ` Jiri Olsa
2023-01-31 22:50 ` Ian Rogers
2023-02-01 2:00 ` Ian Rogers
2023-01-24 23:04 ` [PATCH v4 1/2] tools/resolve_btfids: Install subcmd headers Jiri Olsa
2023-01-25 17: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=167466781681.13690.9875840754457766562.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=connoro@google.com \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=nathan@kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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