From: patchwork-bot+netdevbpf@kernel.org
To: Nathan Chancellor <nathan@kernel.org>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
mykolal@fb.com, bpf@vger.kernel.org, netdev@vger.kernel.org,
patches@lists.linux.dev, llvm@lists.linux.dev,
yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v2] selftests/bpf: Update LLVM Phabricator links
Date: Fri, 12 Jan 2024 02:50:29 +0000 [thread overview]
Message-ID: <170502782940.19866.16464441843592001659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240111-bpf-update-llvm-phabricator-links-v2-1-9a7ae976bd64@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 11 Jan 2024 13:16:48 -0700 you wrote:
> reviews.llvm.org was LLVM's Phabricator instances for code review. It
> has been abandoned in favor of GitHub pull requests. While the majority
> of links in the kernel sources still work because of the work Fangrui
> has done turning the dynamic Phabricator instance into a static archive,
> there are some issues with that work, so preemptively convert all the
> links in the kernel sources to point to the commit on GitHub.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: Update LLVM Phabricator links
https://git.kernel.org/bpf/bpf-next/c/32e14348077c
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:[~2024-01-12 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 20:16 [PATCH bpf-next v2] selftests/bpf: Update LLVM Phabricator links Nathan Chancellor
2024-01-12 2: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=170502782940.19866.16464441843592001659.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=llvm@lists.linux.dev \
--cc=mykolal@fb.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=yonghong.song@linux.dev \
/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