From: Eduard Zingerman <eddyz87@gmail.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: bpf <bpf@vger.kernel.org>, KP Singh <kpsingh@kernel.org>
Subject: Re: Is tools/testing/selftests/bpf/ maintained?
Date: Fri, 13 Oct 2023 17:23:21 +0300 [thread overview]
Message-ID: <343194ce86ae73695d7591c87816938f1f8e4da6.camel@gmail.com> (raw)
In-Reply-To: <c73c0e02-4cc8-4927-bc62-dab33bd98ac4@I-love.SAKURA.ne.jp>
On Fri, 2023-10-13 at 23:17 +0900, Tetsuo Handa wrote:
> Yes, I did something like below and build succeeded. Thank you.
Great :)
> wget https://apt.llvm.org/llvm.sh
> chmod +x llvm.sh
> ./llvm.sh 16
> apt remove clang
> ln -s /usr/bin/clang-16 /usr/bin/clang
I didn't know LLVM has a script to deal with repos, thanks.
next prev parent reply other threads:[~2023-10-13 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 13:39 Is tools/testing/selftests/bpf/ maintained? Tetsuo Handa
2023-10-12 16:34 ` Eduard Zingerman
2023-10-13 13:15 ` Tetsuo Handa
2023-10-13 13:25 ` Eduard Zingerman
2023-10-13 14:17 ` Tetsuo Handa
2023-10-13 14:23 ` Eduard Zingerman [this message]
2023-10-12 16:35 ` Andrii Nakryiko
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=343194ce86ae73695d7591c87816938f1f8e4da6.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=kpsingh@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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