[PW_SID:1086176] Auto-generate maintainer profile entries by linux-riscv-bot · Pull Request #1824 · linux-riscv/linux

linux-riscv-bot · 2026-04-27T15:15:52Z

PR for series 1086176 applied to workflow__riscv__fixes

Name: Auto-generate maintainer profile entries
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=1086176
Version: 4

…_TYPED_FUNC_START After commit 67bdd7b ("riscv: Split out measure_cycles() for reuse") and commit c03ad15 ("riscv: Reuse measure_cycles() in check_vector_unaligned_access()"), there are CFI failure when booting kernels with CONFIG_CFI=y: CFI failure at measure_cycles+0x38/0xe0 (target: __riscv_copy_words_unaligned+0x0/0x50; expected type: ...) CFI failure at measure_cycles+0x38/0xe0 (target: __riscv_copy_vec_words_unaligned+0x0/0x24; expected type: ...) The __riscv_copy_*_unaligned() functions are now called indirectly but they are not defined with SYM_TYPED_FUNC_START, which is required for assembly functions called indirectly from C to pass CFI checking. Switch to SYM_TYPED_FUNC_START to clear up the CFI failures. Fixes: 67bdd7b ("riscv: Split out measure_cycles() for reuse") Fixes: c03ad15 ("riscv: Reuse measure_cycles() in check_vector_unaligned_access()") Signed-off-by: Nathan Chancellor <nathan@kernel.org> Reviewed-by: Sami Tolvanen <samitolvanen@google.com> Reviewed-by: Nam Cao <namcao@linutronix.de> Link: https://patch.msgid.link/20260406-measure_cycles-cfi-failure-v1-1-03e0234ae02f@kernel.org Signed-off-by: Paul Walmsley <pjw@kernel.org>

While this file is really trivial, add a SPDX license line on it. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add a feature to allow auto-generating media entry profiles from the corresponding field inside MAINTAINERS file(s). Suggested-by: Dan Williams <djbw@kernel.org> Closes: https://lore.kernel.org/linux-doc/69dd6299440be_147c801005b@djbw-dev.notmuch/ Acked-by: Dan Williams <djbw@kernel.org> Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Message-ID: <4e9512a3d05942c98361d06d60a118d7c78762b6.1776176108.git.mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Instead of manually creating a TOC tree for them, use the new tag to auto-generate its TOC. Co-developed-by: Dan Williams <djbw@kernel.org> Signed-off-by: Dan Williams <djbw@kernel.org> Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Message-ID: <9228f77b0339b8e5dea4a201ab6d4feb30cef5c2.1776176108.git.mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

As we're picking the name of the subsystem from MAINTAINERS, also use its subsystem name for the titles. Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Some subsystem profiles are maintained elsewhere. Add them to the output. Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

When a maintainer's profile is stored outside process, they're already included on some other book and the name of the filesystem may not be there. That's why the logic picks the name from the subsystem's name. However, files directly placed together with maintainers-handbooks.rst (e.g. under Documentation/process/) is a different history: those aren't placed anywhere, so we can keep using their own names, letting Sphinx do his thing. Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Instead of showing as a "Contents:" with 2 identation levels, drop its title and show profiles as a list of entries. Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

There are three "types" of profiles: 1. Profiles already included inside subsystem-specific documentation. This is the most common case; 2. Profiles that are hosted externally; 3. Profiles that are at the same location as maintainer-handbooks.rst. For (3), we need to create a TOC, as they don't exist elsewhere. Change the logic to create TOC just for (3), prepending the content of maintainer-handbooks with a sorted entry of all types, before the TOC. With such change, we can have an unique sorted list of profiles, having the subsystem names used there listed. Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

os.path.relpath() will do the wrong thing with O=dir, as the build system uses "cd <dir>" internally. Solve it by using app.srcdir, which, on normal cases, point to Documentation/, or, when SPHINXDIRS=process, it will be set with Documentation/process. While here, remove a dead code while writing maintainer profiles, as now all entries should have both profile and entry. Reported-by: Randy Dunlap <rdunlap@infradead.org> Closes: https://lore.kernel.org/linux-doc/88335220-3527-4b1f-9500-417f7ebb7a02@infradead.org/T/#m6854cbd8d30e2c5d3e8c4173bae1c3d6922ff970 Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Change the logic to parse MAINTAINERS file content just once, while still allowing using it multiple times. Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

linux-riscv-bot · 2026-04-27T15:22:46Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 137.30 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T15:38:16Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 929.07 seconds
Result: ERROR
Output:

Redirect to /build/tmp.FJyrV4rjEP and /build/tmp.In4vb3tcTM
Tree base:
01805bc4f902e ("Adding CI files")
Building the whole tree with the patch
error:
Warning: /build/tmp7b26ljz4/drivers/pmdomain/mediatek/mtk-mfg-pmdomain.c:244 struct __packed mtk_mfg_opp_entry { __le32 freq_khz; __le32 voltage_core; __le32 voltage_sram; __le32 posdiv; __le32 voltage_margin; __le32 power_mw; }; error: Cannot parse struct or union!
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_words_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_bytes_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_vec_words_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_vec_bytes_unaligned'; recompile with -fPIC



real	15m20.264s
user	574m11.686s
sys	107m38.984s

linux-riscv-bot · 2026-04-27T16:00:51Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1352.90 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:01:18Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 25.24 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:01:46Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 26.37 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:01:49Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 0.87 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:03:14Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 83.64 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:03:16Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.25 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:03:19Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
kdoc
Desc: Detects for kdoc errors
Duration: 0.91 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:03:21Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:03:23Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:03:25Z

Patch 1: "[v4,01/10] docs: maintainers: add SPDX license to the file"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.32 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:05:54Z

Patch 2: "[v4,02/10] docs: maintainers_include: auto-generate maintainer profile TOC"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 134.20 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:21:27Z

Patch 2: "[v4,02/10] docs: maintainers_include: auto-generate maintainer profile TOC"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 931.03 seconds
Result: ERROR
Output:

Redirect to /build/tmp.RWZD3zz7AY and /build/tmp.r4PAnhU6iS
Tree base:
e013ec2c102c4 ("docs: maintainers: add SPDX license to the file")
Building the whole tree with the patch
error:
Warning: /build/tmpz6v4k5w5/drivers/pmdomain/mediatek/mtk-mfg-pmdomain.c:244 struct __packed mtk_mfg_opp_entry { __le32 freq_khz; __le32 voltage_core; __le32 voltage_sram; __le32 posdiv; __le32 voltage_margin; __le32 power_mw; }; error: Cannot parse struct or union!
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_words_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_bytes_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_vec_words_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_vec_bytes_unaligned'; recompile with -fPIC



real	15m21.749s
user	576m1.705s
sys	108m17.086s

linux-riscv-bot · 2026-04-27T16:44:03Z

Patch 2: "[v4,02/10] docs: maintainers_include: auto-generate maintainer profile TOC"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1354.70 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:44:31Z

Patch 2: "[v4,02/10] docs: maintainers_include: auto-generate maintainer profile TOC"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 25.50 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:44:59Z

Patch 2: "[v4,02/10] docs: maintainers_include: auto-generate maintainer profile TOC"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 26.75 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T16:45:02Z

Patch 2: "[v4,02/10] docs: maintainers_include: auto-generate maintainer profile TOC"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 0.73 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:06:04Z

Patch 8: "[v4,08/10] docs: maintainers_include: improve its output"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.34 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:08:35Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 135.73 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:24:05Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 927.75 seconds
Result: ERROR
Output:

Redirect to /build/tmp.uGXzQuWvDt and /build/tmp.CokMy6vIqh
Tree base:
aee3ff61704d0 ("docs: maintainers_include: improve its output")
Building the whole tree with the patch
error:
Warning: /build/tmp4qdcbwtz/drivers/pmdomain/mediatek/mtk-mfg-pmdomain.c:244 struct __packed mtk_mfg_opp_entry { __le32 freq_khz; __le32 voltage_core; __le32 voltage_sram; __le32 posdiv; __le32 voltage_margin; __le32 power_mw; }; error: Cannot parse struct or union!
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_words_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_bytes_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_vec_words_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_vec_bytes_unaligned'; recompile with -fPIC



real	15m18.831s
user	572m57.943s
sys	107m32.722s

linux-riscv-bot · 2026-04-27T21:46:37Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1350.40 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:47:03Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 24.87 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:47:31Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 26.54 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:47:34Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 0.72 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:49:00Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 85.24 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:49:02Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.49 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:49:05Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
kdoc
Desc: Detects for kdoc errors
Duration: 0.96 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:49:07Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:49:09Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:49:11Z

Patch 9: "[v4,09/10] docs: maintainers_include: fix support for O=dir"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.32 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T21:51:42Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 136.88 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:07:16Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 932.27 seconds
Result: ERROR
Output:

Redirect to /build/tmp.l2KyS3WXzr and /build/tmp.OZ8cOkzSTH
Tree base:
f4a6afd7f890d ("docs: maintainers_include: fix support for O=dir")
Building the whole tree with the patch
error:
Warning: /build/tmp572pwoz2/drivers/pmdomain/mediatek/mtk-mfg-pmdomain.c:244 struct __packed mtk_mfg_opp_entry { __le32 freq_khz; __le32 voltage_core; __le32 voltage_sram; __le32 posdiv; __le32 voltage_margin; __le32 power_mw; }; error: Cannot parse struct or union!
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_vec_words_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_vec_bytes_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_words_unaligned'; recompile with -fPIC
ld.lld: error: relocation R_RISCV_32 cannot be used against symbol '__kcfi_typeid___riscv_copy_bytes_unaligned'; recompile with -fPIC



real	15m23.675s
user	573m26.035s
sys	107m41.950s

linux-riscv-bot · 2026-04-27T22:29:49Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1350.46 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:30:16Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 25.19 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:30:44Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 26.33 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:30:46Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 0.75 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:32:15Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 87.52 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:32:17Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:32:19Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
kdoc
Desc: Detects for kdoc errors
Duration: 0.90 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:32:21Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:32:23Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2026-04-27T22:32:24Z

Patch 10: "[v4,10/10] docs: maintainers_include: parse MAINTAINERS just once"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.32 seconds
Result: PASS

nathanchance and others added 12 commits April 24, 2026 07:25

Adding CI files

01805bc

docs: maintainers: add SPDX license to the file

e013ec2

While this file is really trivial, add a SPDX license line on it. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

linux-riscv-bot force-pushed the workflow__riscv__fixes branch 3 times, most recently from f190ec6 to 2c3b264 Compare May 2, 2026 08:13

linux-riscv-bot closed this May 5, 2026

linux-riscv-bot deleted the pw1086176 branch May 5, 2026 02:06

Conversation

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026

Uh oh!

linux-riscv-bot commented Apr 27, 2026