* [PATCH 2/2] rust: enable `too-long-first-doc-paragraph` clippy lint [not found] <20250216213827.3752586-1-benno.lossin@proton.me> @ 2025-02-16 21:38 ` Benno Lossin 2025-02-16 21:46 ` Charalampos Mitrodimas 2025-02-17 18:07 ` Miguel Ojeda 0 siblings, 2 replies; 4+ messages in thread From: Benno Lossin @ 2025-02-16 21:38 UTC (permalink / raw) To: Masahiro Yamada, Nathan Chancellor, Nicolas Schier, Miguel Ojeda, Alex Gaynor, Boqun Feng, Gary Guo, Björn Roy Baron, Benno Lossin, Andreas Hindborg, Alice Ryhl, Trevor Gross, Danilo Krummrich Cc: linux-kbuild, linux-kernel, rust-for-linux Introduced in Rust 1.82.0 [1], this lint ensures that the first line of documentation is short. That is because those lines get rendered in the html version of the docs directly next to the items and should therefore be short. Additionally, a short first sentence might help developers remember the rest of the documentation if they have read it already before. Reviewers have pointed this out manually on several occasions, thus enable the lint. Here is an example error fixed in the previous commit: error: first doc comment paragraph is too long --> rust/kernel/driver.rs:13:1 | 13 | / /// The [`RegistrationOps`] trait serves as generic interface for subsystems (e.g., PCI, Platform, 14 | | /// Amba, etc.) to provide the corresponding subsystem specific implementation to register / 15 | | /// unregister a driver of the particular type (`RegType`). 16 | | /// 17 | | /// For instance, the PCI subsystem would set `RegType` to `bindings::pci_driver` and call | |_^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph = note: `-D clippy::too-long-first-doc-paragraph` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::too_long_first_doc_paragraph)]` error: aborting due to 1 previous error The exact length can be configured in the .clippy.toml if we need to do so. Link: https://github.com/rust-lang/rust-clippy/issues/12989 [1] Signed-off-by: Benno Lossin <benno.lossin@proton.me> --- Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/Makefile b/Makefile index 9e0d63d9d94b..d00cbeb63714 100644 --- a/Makefile +++ b/Makefile @@ -486,6 +486,7 @@ export rust_common_flags := --edition=2021 \ -Wclippy::undocumented_unsafe_blocks \ -Wclippy::unnecessary_safety_comment \ -Wclippy::unnecessary_safety_doc \ + -Wclippy::too-long-first-doc-paragraph \ -Wrustdoc::missing_crate_level_docs \ -Wrustdoc::unescaped_backticks -- 2.47.2 ^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH 2/2] rust: enable `too-long-first-doc-paragraph` clippy lint 2025-02-16 21:38 ` [PATCH 2/2] rust: enable `too-long-first-doc-paragraph` clippy lint Benno Lossin @ 2025-02-16 21:46 ` Charalampos Mitrodimas 2025-02-17 18:07 ` Miguel Ojeda 1 sibling, 0 replies; 4+ messages in thread From: Charalampos Mitrodimas @ 2025-02-16 21:46 UTC (permalink / raw) To: Benno Lossin Cc: Masahiro Yamada, Nathan Chancellor, Nicolas Schier, Miguel Ojeda, Alex Gaynor, Boqun Feng, Gary Guo, Björn Roy Baron, Andreas Hindborg, Alice Ryhl, Trevor Gross, Danilo Krummrich, linux-kbuild, linux-kernel, rust-for-linux Benno Lossin <benno.lossin@proton.me> writes: > Introduced in Rust 1.82.0 [1], this lint ensures that the first line of > documentation is short. That is because those lines get rendered in the > html version of the docs directly next to the items and should therefore > be short. > Additionally, a short first sentence might help developers remember the > rest of the documentation if they have read it already before. > > Reviewers have pointed this out manually on several occasions, thus > enable the lint. > > Here is an example error fixed in the previous commit: > > error: first doc comment paragraph is too long > --> rust/kernel/driver.rs:13:1 > | > 13 | / /// The [`RegistrationOps`] trait serves as generic interface for subsystems (e.g., PCI, Platform, > 14 | | /// Amba, etc.) to provide the corresponding subsystem specific implementation to register / > 15 | | /// unregister a driver of the particular type (`RegType`). > 16 | | /// > 17 | | /// For instance, the PCI subsystem would set `RegType` to `bindings::pci_driver` and call > | |_^ > | > = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph > = note: `-D clippy::too-long-first-doc-paragraph` implied by `-D warnings` > = help: to override `-D warnings` add `#[allow(clippy::too_long_first_doc_paragraph)]` > > error: aborting due to 1 previous error > > The exact length can be configured in the .clippy.toml if we need to do > so. > > Link: https://github.com/rust-lang/rust-clippy/issues/12989 [1] > Signed-off-by: Benno Lossin <benno.lossin@proton.me> > --- > Makefile | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Makefile b/Makefile > index 9e0d63d9d94b..d00cbeb63714 100644 > --- a/Makefile > +++ b/Makefile > @@ -486,6 +486,7 @@ export rust_common_flags := --edition=2021 \ > -Wclippy::undocumented_unsafe_blocks \ > -Wclippy::unnecessary_safety_comment \ > -Wclippy::unnecessary_safety_doc \ > + -Wclippy::too-long-first-doc-paragraph \ > -Wrustdoc::missing_crate_level_docs \ > -Wrustdoc::unescaped_backticks Reviewed-by: Charalampos Mitrodimas <charmitro@posteo.net> ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 2/2] rust: enable `too-long-first-doc-paragraph` clippy lint 2025-02-16 21:38 ` [PATCH 2/2] rust: enable `too-long-first-doc-paragraph` clippy lint Benno Lossin 2025-02-16 21:46 ` Charalampos Mitrodimas @ 2025-02-17 18:07 ` Miguel Ojeda 2025-02-17 22:49 ` Benno Lossin 1 sibling, 1 reply; 4+ messages in thread From: Miguel Ojeda @ 2025-02-17 18:07 UTC (permalink / raw) To: Benno Lossin Cc: Masahiro Yamada, Nathan Chancellor, Nicolas Schier, Miguel Ojeda, Alex Gaynor, Boqun Feng, Gary Guo, Björn Roy Baron, Andreas Hindborg, Alice Ryhl, Trevor Gross, Danilo Krummrich, linux-kbuild, linux-kernel, rust-for-linux On Sun, Feb 16, 2025 at 10:38 PM Benno Lossin <benno.lossin@proton.me> wrote: > > Introduced in Rust 1.82.0 [1], this lint ensures that the first line of We will need to ignore unknown lints so that it does not warn on older compilers. We should probably do it conditionally instead -- it requires some rework to do it for everything, but we can easily do it for kernel code. I can tweak it and put this patch into my warning rework series -- I had to send the v2 of that anyway. Sounds good? Thanks! Cheers, Miguel ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 2/2] rust: enable `too-long-first-doc-paragraph` clippy lint 2025-02-17 18:07 ` Miguel Ojeda @ 2025-02-17 22:49 ` Benno Lossin 0 siblings, 0 replies; 4+ messages in thread From: Benno Lossin @ 2025-02-17 22:49 UTC (permalink / raw) To: Miguel Ojeda Cc: Masahiro Yamada, Nathan Chancellor, Nicolas Schier, Miguel Ojeda, Alex Gaynor, Boqun Feng, Gary Guo, Björn Roy Baron, Andreas Hindborg, Alice Ryhl, Trevor Gross, Danilo Krummrich, linux-kbuild, linux-kernel, rust-for-linux On 17.02.25 19:07, Miguel Ojeda wrote: > On Sun, Feb 16, 2025 at 10:38 PM Benno Lossin <benno.lossin@proton.me> wrote: >> >> Introduced in Rust 1.82.0 [1], this lint ensures that the first line of > > We will need to ignore unknown lints so that it does not warn on older > compilers. > > We should probably do it conditionally instead -- it requires some > rework to do it for everything, but we can easily do it for kernel code. Ah yeah forgot about that. That's a good point. > I can tweak it and put this patch into my warning rework series -- I > had to send the v2 of that anyway. Sounds good? Sure! --- Cheers, Benno ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2025-02-17 22:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20250216213827.3752586-1-benno.lossin@proton.me>
2025-02-16 21:38 ` [PATCH 2/2] rust: enable `too-long-first-doc-paragraph` clippy lint Benno Lossin
2025-02-16 21:46 ` Charalampos Mitrodimas
2025-02-17 18:07 ` Miguel Ojeda
2025-02-17 22:49 ` Benno Lossin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox