summaryrefslogtreecommitdiff
path: root/block/ioprio.c
diff options
context:
space:
mode:
authorMiguel Ojeda <ojeda@kernel.org>2023-06-16 03:16:24 +0300
committerMiguel Ojeda <ojeda@kernel.org>2023-08-09 20:33:31 +0300
commitaac284b1eb420c9317475cacdd21dd0ae3c3eda8 (patch)
tree7bfa0c1b49c9b4081d3a1de899810a1668197dd9 /block/ioprio.c
parenteae90172c5b89f08f054b959197397c5cadd658d (diff)
downloadlinux-aac284b1eb420c9317475cacdd21dd0ae3c3eda8.tar.xz
kbuild: rust_is_available: print docs reference
People trying out the Rust support in the kernel may get warnings and errors from `scripts/rust_is_available.sh` from the `rustavailable` target or the build step. Some of those users may be following the Quick Start guide, but others may not (likely those getting warnings from the build step instead of the target). While the messages are fairly clear on what the problem is, it may not be clear how to solve the particular issue, especially for those not aware of the documentation. We could add all sorts of details on the script for each one, but it is better to point users to the documentation instead, where it is easily readable in different formats. It also avoids duplication. Thus add a reference to the documentation whenever the script fails or there is at least a warning. Reviewed-by: Finn Behrens <fin@nyantec.com> Reviewed-by: Masahiro Yamada <masahiroy@kernel.org> Reviewed-by: Nathan Chancellor <nathan@kernel.org> Reviewed-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com> Link: https://lore.kernel.org/r/20230616001631.463536-5-ojeda@kernel.org Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Diffstat (limited to 'block/ioprio.c')
0 files changed, 0 insertions, 0 deletions