srdusr
aboutsummaryrefslogtreecommitdiffstats
path: root/crates/wayland/src/output_power.rs
diff options
context:
space:
mode:
authorsrdusr <[email protected]>2024-08-03 20:07:00 +0200
committersrdusr <[email protected]>2024-08-03 20:07:00 +0200
commit35a28a257644483495ac2bd6a5fb1e109e8c1f26 (patch)
tree37944a7a2a61bf7ff977fa6349742d1a53ed5ad3 /crates/wayland/src/output_power.rs
parentf166df4d979162ae09b439c87cdc64f2b0981308 (diff)
downloadsrdwm-35a28a257644483495ac2bd6a5fb1e109e8c1f26.tar.gz
srdwm-35a28a257644483495ac2bd6a5fb1e109e8c1f26.zip
Fix doc-comment file references left stale by today's six module splits
~17 comments across the codebase still pointed at udev.rs/winit.rs/ state.rs by their old flat-file names after those became udev/, winit/, state/ directories - found while auditing what this work rushed, since the split verification (function/struct-name diffing, full test suite) checked structural correctness but never comment accuracy. Updated each to either the specific new file (e.g. "see state.rs's REPEAT_DELAY" -> "see state/mod.rs's REPEAT_DELAY", "udev.rs's monitors()" -> "udev/platform.rs's monitors()") or the bare module name where the reference was already generic ("the udev/winit backends", not a specific location).
Diffstat (limited to 'crates/wayland/src/output_power.rs')
-rw-r--r--crates/wayland/src/output_power.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/crates/wayland/src/output_power.rs b/crates/wayland/src/output_power.rs
index e0734f8..298c59c 100644
--- a/crates/wayland/src/output_power.rs
+++ b/crates/wayland/src/output_power.rs
@@ -9,7 +9,7 @@
//! Neither protocol implies the other.
//!
//! DRM/udev backend only: there is no real display to power down when
-//! nested under a host compositor (`winit.rs`) - the host owns the actual
+//! nested under a host compositor (`winit`) - the host owns the actual
//! screen, and turning off the *nested window* makes no sense. The global
//! is simply never created there (`CompState::_output_power_state` is
//! `None`), so a client sees the protocol as genuinely unsupported rather