From: Kees Cook <keescook@chromium.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: akpm@linux-foundation.org, llvm@lists.linux.dev,
patches@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kvm@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-trace-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-pm@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-efi@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
linux-arch@vger.kernel.org, kasan-dev@googlegroups.com,
linux-mm@kvack.org, bridge@lists.linux.dev,
netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kselftest@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, mykolal@fb.com,
bpf@vger.kernel.org
Subject: Re: [PATCH 0/3] Update LLVM Phabricator and Bugzilla links
Date: Wed, 10 Jan 2024 16:46:06 -0800 [thread overview]
Message-ID: <202401101645.ED161519BA@keescook> (raw)
In-Reply-To: <20240109-update-llvm-links-v1-0-eb09b59db071@kernel.org>
On Tue, Jan 09, 2024 at 03:16:28PM -0700, Nathan Chancellor wrote:
> This series updates all instances of LLVM Phabricator and Bugzilla links
> to point to GitHub commits directly and LLVM's Bugzilla to GitHub issue
> shortlinks respectively.
>
> I split up the Phabricator patch into BPF selftests and the rest of the
> kernel in case the BPF folks want to take it separately from the rest of
> the series, there are obviously no dependency issues in that case. The
> Bugzilla change was mechanical enough and should have no conflicts.
>
> I am aiming this at Andrew and CC'ing other lists, in case maintainers
> want to chime in, but I think this is pretty uncontroversial (famous
> last words...).
>
> ---
> Nathan Chancellor (3):
> selftests/bpf: Update LLVM Phabricator links
> arch and include: Update LLVM Phabricator links
> treewide: Update LLVM Bugzilla links
>
> arch/arm64/Kconfig | 4 +--
> arch/powerpc/Makefile | 4 +--
> arch/powerpc/kvm/book3s_hv_nested.c | 2 +-
> arch/riscv/Kconfig | 2 +-
> arch/riscv/include/asm/ftrace.h | 2 +-
> arch/s390/include/asm/ftrace.h | 2 +-
> arch/x86/power/Makefile | 2 +-
> crypto/blake2b_generic.c | 2 +-
> drivers/firmware/efi/libstub/Makefile | 2 +-
> drivers/gpu/drm/amd/amdgpu/sdma_v4_4_2.c | 2 +-
> drivers/media/test-drivers/vicodec/codec-fwht.c | 2 +-
> drivers/regulator/Kconfig | 2 +-
> include/asm-generic/vmlinux.lds.h | 2 +-
> include/linux/compiler-clang.h | 2 +-
> lib/Kconfig.kasan | 2 +-
> lib/raid6/Makefile | 2 +-
> lib/stackinit_kunit.c | 2 +-
> mm/slab_common.c | 2 +-
> net/bridge/br_multicast.c | 2 +-
> security/Kconfig | 2 +-
> tools/testing/selftests/bpf/README.rst | 32 +++++++++++-----------
> tools/testing/selftests/bpf/prog_tests/xdpwall.c | 2 +-
> .../selftests/bpf/progs/test_core_reloc_type_id.c | 2 +-
> 23 files changed, 40 insertions(+), 40 deletions(-)
> ---
> base-commit: 0dd3ee31125508cd67f7e7172247f05b7fd1753a
> change-id: 20240109-update-llvm-links-d03f9d649e1e
>
> Best regards,
> --
> Nathan Chancellor <nathan@kernel.org>
>
Excellent! Thanks for doing this. I spot checked a handful I was
familiar with and everything looks good to me.
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
next prev parent reply other threads:[~2024-01-11 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 22:16 [PATCH 0/3] Update LLVM Phabricator and Bugzilla links Nathan Chancellor
2024-01-09 22:16 ` [PATCH 1/3] selftests/bpf: Update LLVM Phabricator links Nathan Chancellor
2024-01-11 4:05 ` Yonghong Song
2024-01-11 19:40 ` Nathan Chancellor
2024-01-11 20:00 ` Alexei Starovoitov
2024-01-11 20:20 ` Nathan Chancellor
2024-01-09 22:16 ` [PATCH 2/3] arch and include: " Nathan Chancellor
2024-01-10 13:48 ` Conor Dooley
2024-01-09 22:16 ` [PATCH 3/3] treewide: Update LLVM Bugzilla links Nathan Chancellor
2024-01-11 0:46 ` Kees Cook [this message]
2024-01-11 20:34 ` [PATCH 0/3] Update LLVM Phabricator and " Fangrui Song
2024-01-12 14:52 ` Alex Deucher
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=202401101645.ED161519BA@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=bridge@lists.linux.dev \
--cc=daniel@iogearbox.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=kasan-dev@googlegroups.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=mykolal@fb.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patches@lists.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;
as well as URLs for NNTP newsgroup(s).